Level Extreme platform
Subscription
Corporate profile
Products & Services
Support
Legal
Français
Running external Programs
Message
General information
Forum:
Visual FoxPro
Category:
Coding, syntax & commands
Environment versions
Visual FoxPro:
VFP 5
OS:
Windows 2000 SP2
Database:
Visual FoxPro
Miscellaneous
Thread ID:
00966740
Message ID:
00966971
Views:
16
>>>One of the solutions is:
>>>
>>>DECLARE INTEGER WinExec IN win32api ;
>>>   STRING command, INTEGER nShow
>>>
>>>=WinExec("exename.exe parameter",1)
>>
>>Yuri,
>>
>>This function is provided strictly for backward compatibility with Win16 based apps.
>
>Thank you, George. Good to know it.
>By the way, so happened, I currently support projects which were created long time ago, gradually being updated when needed, and which have winexe in many VFP8 modules. What would be your recommendation? To replace all Winexec there (just in case) or leave them as is?

Yuri,

Basically, I'd say that "if it ain't broke, don't fix it". However, in the future, I'd recommend either the ShellExecute() function or using the WScript.Shell's run method, depending on the platform. If it's Win2K or above, I'd go with the latter.
George

Ubi caritas et amor, deus ibi est
Previous
Next
Reply
Map
View

Click here to load this message in the networking platform