FPW2.6a Run WinWord

[tfs2001]

fpw 2.6a created 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 c:\auxwin, exe program in sub-dir c:\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 created 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.

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.

 

[gpalmer711]

You will be better off asking this in the Fox Pro forum here forum182

Greg Palmer
Free Software for Adminstrators

http://www.palmersoft.co.uk

 

[tfs2001]

Thank you for your response, I have already listed this problem on fox pro (old version), but without any luck. I have added two new lines to my program as follow:

cd ? getenv('path')

the app file responds with

c:\windows\system32;c:\dos;c:\windows;c:\windows\system32\wbem;c:\progra~1\micros~1\office10;c:\dos

the exe file responds with

c:\dos;c:\windows\system32

I do not know XP but I think this must have something to do with a security issue.

 

[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.