17 replies to this topic

[Wim Soutendijk]

Did you include the full path name in your SYSTEM command?

[Rob Donovan]

Hi,

To run the command on the server...

#X = SYSTEM('dir >dir.txt')

To run the command on the client PC...

#X = SYSTEM('GUI WINDOWS dir >dir.txt')

Rob D

[Wim Soutendijk]

Yes I am able to execute at lease a .bat script located on the win2000 server

[DARREN]

there is a new method available to developers on version 5 for running client side apps called client.execute()

This replaces the GUI WINDOWS system command and can also reference logical paths e.g. CLIENT.EXECUTE(%MYPATH%MYPROGRAM.EXE)where MYPATH is an entry in the proivconst.ini

This is a much cleaner way of invoking programs on the client side.

[Glenn Meyers]

An oldie but a goodie.......
I have a similar problem as above.

I cannot get :
#X = SYSTEM('GUI WINDOWS dir >dir.txt')
to run and create a file on the drive. It "runs" and returns and the function carries on, but no joy on the data file .

I get a stop button with the message "Unable to execute local command" message.

The command was entered as above in Logic In of a screen function. My host systems is an HP Unix platform running 4.6. The client is a windows 2000 based PC. Client is 5.0EA Build 283 Dated July 3, 2001.
ProIV has no newer clients for 4.6 that I am aware of.

I have made a function work to dump to an Excel Spreadsheet using:
#RC = SYSTEM("GUI WINDOWS ASYNC EXCEL")
but I still get that same stop button/message before the write to Excel begins and it is horribly slow.

Ultimately what I am trying to do is have the SYSTEM command pop up an IExplorer session with a diagram of a manufacturing configuration. This function sits on the manufacturing line and the user will scan in a serialized part. The assembly instructions (a jpeg) will then pop up on the screen for the assembler.

Ideas anyone???

Thanks in advance!

Glenn

Edited by Glenn Meyers, 08 July 2003 - 07:24 PM.

[Andy Jones]

I cannot get :
#X = SYSTEM('GUI WINDOWS dir >dir.txt')
to run and create a file on the drive. It "runs" and returns and the function carries on, but no joy on the data file .

I get a stop button with the message "Unable to execute local command" message.

The reason your DIR command doesn't work is because you've used the WINDOWS keyword. It's only of use when you are intending to run an executable file (program or batch file).
In your example DIR is a shell command.

To execute shell commands such as DIR, just drop the 'WINDOWS' part.
i.e. #X = SYSTEM('GUI dir >dir.txt')

That should work!

[Glenn Meyers]

Thanks for the response Andy.
Well, It worked and it didn't.
It worked in that ProIV didn't choke on it and send up the button/message.
No joy on the creation of a file on the C drive, however.

While I'm still struggling with this....any other ideas????

Thanks!

Glenn

[Rob Donovan]

Hi,

Could it be that its creating it in the ProIV startup dir, or somewhere else?

Does it work if you put on a path?

#X = SYSTEM('GUI dir > c:\temp\dir.txt')

Rob D.

[Glenn Meyers]

Das ist GOODT!

With a path it worked correctly.

Now, How do I get it to call Windows Explorer?

Thanks Guys!

Glenn

[Rob Donovan]

OK... try this....

#X = SYSTEM("GUI WINDOWS EXPLORER")

But ProIV will not wait for the windwos command to finish.. It continues, once the windows prog has started.

Rob D.

[Glenn Meyers]

Editing the above failed so here goes again:

I have tried:

THIS worked correctly:
#RC = SYSTEM(“GUI WINDOWS NOTEPAD.EXE”)

This did NOT work:
$CMD = '/C "C:\PROGRAM FILES\INTERNET EXPLORER\IEXPLORE.EXE" ' +
'HTTP://WWW.GOOGLE.COM'
#X = SYSTEM('GUI WINDOWS ASYNC' + $CMD)
I tried the above with all combinations of WINDOWS, ASYNC, and the /C command for older clients.

This too did not work with all combinations of WINDOWS and ASYNC:
$CMD = ' C:\Program Files\Internet Explorer\IExplore.EXE'
#RC = SYSTEM("GUI WINDOWS ASYNC" + $CMD)

Still stumped....or am I expecting too much???
Glenn

[Glenn Meyers]

Rob,

#X = SYSTEM("GUI WINDOWS EXPLORER")

Did work.

Glenn