Level Extreme platform
Subscription
Corporate profile
Products & Services
Support
Legal
Français
Size of 'run window'
Message
From
29/05/2004 12:47:12
Dragan Nedeljkovich (Online)
Now officially retired
Zrenjanin, Serbia
 
General information
Forum:
Visual FoxPro
Category:
Coding, syntax & commands
Miscellaneous
Thread ID:
00908233
Message ID:
00908457
Views:
24
>Dragan,
>
>Thank you for the suggestion.
>
>Two questsions:
>1. Do you know if any compatibilty issues going back to W98SE?
>2. I looked at it only briefly and could not find any examples. Do you know if any exists (possibly outside of the class itself)?

ad 1. No - I'm using it for four years now, and I think it even ran on some W95 boxes. The API functions it uses seem to be very old ones, which didn't change (in the interface, that is) over time.

ad 2. Here's how I use it: I write a batch file with my zip command (using pkzip25 - the good old command-line thingy), with all the parameters etc. Then,
	lcbatFile=Fullpath(Forceext(Sys(2015),"bat"))
TEXT textmerge noshow to lcBat
pkzip25 -add=update -dire <<lcZipName>>  @<<listfile>> ><<logfile>>
ENDTEXT
	lcThere=Fullpath(".")
	Strtofile(lcBat, lcbatFile)
	Local oprocess As api_apprun Of Process.vcx
	oprocess=Newobject('api_apprun','process', '', lcbatFile, lcThere, 'HID')
	oprocess.LaunchAppAndWait()
	Release oprocess
	Erase (lcbatFile)
The major point is using full path for the location of where the process is supposed to run - but that's something you have to pay attention to even with a Run command. The full path for the batch file (or whatever command you are running) is maybe not necessary, but I still supply it, just to be on the safe side.

back to same old

the first online autobiography, unfinished by design
What, me reckless? I'm full of recks!
Balkans, eh? Count them.
Previous
Next
Reply
Map
View

Click here to load this message in the networking platform