Level Extreme platform
Subscription
Corporate profile
Products & Services
Support
Legal
Français
Execscript is lost in space
Message
General information
Forum:
Visual FoxPro
Category:
Coding, syntax & commands
Miscellaneous
Thread ID:
00878108
Message ID:
00878584
Views:
28
I did an EXECSCRIPT a little while back:
lVoid=EXECSCRIPT(WPARENT()+[.Activate])
and it did as expected!

My understanding is that it can execute a bunch of lines of code, like command window block copy to clip text (w/ CRs and LFs evun):
lVoid=EXECSCRIPT(_cliptext)
Why do the difficulties always wait till we are fully committed to a given strategy. I still gamble. I would hammer it until it worked as I expect it do work. Sometimes I have to make a compromise (or two<g>).

Hack it through the command window, until you spot some compromise code or beat it!

>Sure but the script also sets up the current directory, and many other environmental features. I suppose that they could all be handled by parameters to a program though. Too bad execscript knows nothing about the EXE or APP.
>
>Glenn
>
>>>I have a problem trying to :
>>>
>>>report form whoha to print
>>>
>>>from and execscript. It seems the execscript does not search the executable for reports or forms. How can the executable be referenced in the "report form " statement?
>>>
>>>Glenn
>>
>>Do you have to use execscript?
>>Could you pass the format as a reference and make it work in a prg?
>>
report form (lcwhoha) to print
>>* or
>>report form &lcwhoha to print
>>PS
>>I did not test! You can test it from the command window!
Imagination is more important than knowledge
Previous
Reply
Map
View

Click here to load this message in the networking platform