fullpath() run winword problem 3

[tfs2001]

fpw 2.6a exe file runs on win 3.1 to win 2000, word6 to word2000. Runs on xp pro but cannot connect thru to word2002. User with admin rights, changed path to include winword.exe. Source code in sub-dir auxwin, exe program in sub-dir auxcal. Running fpw, word and exe file in win95 compatibilty and run in 256 colors. From dos in either sub-dir type winword and works fine. From fpw type 'run /n3 winword' in either sub-dir works fine, fullpath('winword.exe',1) returns path to winword.exe. Run fpw app file in auxwin and everything works fine. run fpw exe file in auxcal and 'run /n3 winword' returns 'run /! command failed' and fullpath('winword.exe',1) returns 'c:\auxcal\winword.exe', which tells me that it could not find winword.exe files. I been working with foxpro starting with foxbase 1.06 and I never been this confused.

 

[tfs2001]

Update to my post app & exe files were created in fpw26a

 

[DSummZZZ]

Are you sure you have the correct path set in the exe?
I.e., all spaces removed, 8.3 syntax?
Are you using the same CONFIG.FPW file? Same startup .prg?

Since the .app runs but the .exe doesn't, there must be something in the developement environment that is different than run-time.

-Dave Summers-

Even more Fox stuff at:

http://www.davesummers.net/foxprolinks.htm

 

[tfs2001]

Thank you for your reply and helpful hints. Let me give you a little more infor.

all source files are located in c:\auxwin, the app file is created and run in this sub-dir. the exe file is created in c:\auxcal and all dbf's and cdx's are copied to c:\auxcal. The program command is 'run /n3 winword' and I also added a seperate command 'fullpath('winword.exe',1)' to display the path to winword.exe. the app runs winword without problems and the fullpath() returns 'c:\progra~1\micros~1\office10\winword.exe'. The exe file cannot run winword and the fullpath() returns 'c:\auxcal\winword.exe'. if I change the run command to 'run /n3 c:\progra~1\micros~1\office10\winword.exe' the exe file runs without problems. This problem only occurs on xp pro, I am not experience with xp pro. This is someone else laptop that I am trying to load this program on.

 

[ChrisCarroll]

It's a bit time consuming, but one way to debug this kind of thing is to replace the 'run /n3 winword' with

run cmd

which will allow you to check that the XP path really is what you think it is; and doesn't for instance include relative paths broken by the change of directory

 

[costy]

for w98 or xp i use command
to use database param.dbf .Write in this DBF, path for for winword. fullpath return path after command SET DEFA .

run start /max <dirword>\winword.exe

if in *.app (*.prg) cd to <dirword>\winword.exe after run command work corectly application 32b with start in 16b
Read help in w98 or xp command start
2- Read commadn set path
AA=GETFILE() && SEARCE WINWORD
SET PATH TO &AA
RUN ......

 

[tfs2001]

I WOULD LIKE TO THANK EVERYONE FOR THEIR HELP. THE SOLUTION TO THIS PROBLEM WAS TO ADD THE WINWORD PATH TO THE AUTOEXEC.NT FILE. RUNNING FPW2.6A AND WORD 2002 VIA DDE CAUSED THE PATH TO CHANGE TO THE AUTOEXEC.NT PATH. THIS LAPTOP WAS UPGRADED FROM WIN98 TO WINME AND THEN TO XP PRO.