Has anyone ever interfaced a 3rd party application using Pro-IV? My project is to pass a DOS file from within a Pro-IV function make a call to a 3rd party function which will read the file and write a value back into it which I then have to get and use to continue processing. I'd be grateful for any info or pointers on how this is done. Thank you.
Click the link below to see the new game I'm developing!
Interfaces
Started by
Guest_Andy McBride_*
, May 16 2000 02:56 PM
7 replies to this topic
#2
Rob Donovan
-
- Admin
-
- 1,652 posts
rob@proivrc.com
- Gender:Male
- Location:Spain
Posted 16 May 2000 - 04:19 PM
Hi,
We use flat files (DOS files??) to communicate with a 3rd party software.
PROIV functions write out a SEQ file to a directory. The 3rd party software will then update this file. PROIV can wait until the 3rd party software has finished and then read the output that the program generated.
Is this what you want? Or do you need more info?
Rob
We use flat files (DOS files??) to communicate with a 3rd party software.
PROIV functions write out a SEQ file to a directory. The 3rd party software will then update this file. PROIV can wait until the 3rd party software has finished and then read the output that the program generated.
Is this what you want? Or do you need more info?
Rob
#3
Guest_Andy McBride_*
Guest_Andy McBride_*
-
- Guests
Posted 16 May 2000 - 04:47 PM
Rob,
Thank you for your response. I know about the seq files and have used them many times. I guess what I really want to know is how to call the external routine and how to set up my pro-iv function to wait for the data being returned. Do I use a global logic to call the external routine? Does pro-iv then wait and the return from the external to the gloval is automatic logic?
Thank you for your response. I know about the seq files and have used them many times. I guess what I really want to know is how to call the external routine and how to set up my pro-iv function to wait for the data being returned. Do I use a global logic to call the external routine? Does pro-iv then wait and the return from the external to the gloval is automatic logic?
#4
Chris Pepper
-
- Members
-
- 369 posts
ProIV Guru
- Gender:Male
- Location:United Kingdom
Posted 16 May 2000 - 05:01 PM
Well normally a SYSTEM (or SYSTEM-CRT) command is used to call the external routine. PRO-IV waits for the external routine to complete before continuing. What platform are you running on?
#5
Rob Donovan
-
- Admin
-
- 1,652 posts
rob@proivrc.com
- Gender:Male
- Location:Spain
Posted 16 May 2000 - 05:06 PM
Hi,
I work on a UNIX system not DOS but,
This line of logic will execute the program named 'progname.exe' in the current directory. PROIV will wait until the 'progname.exe' program has finished before the next line of logic is executed.
There are some 'special' parameters (GUI,WINDOWS & ASYNC) used for the SYSTEM command with the windows version of PROIV.
GUI - Run command on the client.
WINDOWS - Run the command directly to the WIN API
ASYNC - Don't wait of the command to finish before returning to PROIV.
eg
This line will run the 'NOTEPAD' application on the client side.
For more info have a look at the 'SYSTEM' command in the LOGIC manual.
Rob
I work on a UNIX system not DOS but,
#X = SYSTEM('progname.exe')This line of logic will execute the program named 'progname.exe' in the current directory. PROIV will wait until the 'progname.exe' program has finished before the next line of logic is executed.
There are some 'special' parameters (GUI,WINDOWS & ASYNC) used for the SYSTEM command with the windows version of PROIV.
GUI - Run command on the client.
WINDOWS - Run the command directly to the WIN API
ASYNC - Don't wait of the command to finish before returning to PROIV.
eg
#X = SYSTEM('GUI WINDOWS NOTEPAD')This line will run the 'NOTEPAD' application on the client side.
For more info have a look at the 'SYSTEM' command in the LOGIC manual.
Rob
#8
Lee Mulheron
-
- Members
-
- 16 posts
Member
- Gender:Male
- Location:UK
Posted 17 May 2000 - 07:48 AM
Hi Andy,
I seem to remember (it been a couple of years) that if the proiv kernel resides on an NT server you can also use :
#X = SYSTEM('GUI C: /C PROGNAME')
where PROGNAME is the path of executable.
This will then run the command from the server (assuming the WINNT directory resides on the C: on the server).
Lee.
I seem to remember (it been a couple of years) that if the proiv kernel resides on an NT server you can also use :
#X = SYSTEM('GUI C: /C PROGNAME')
where PROGNAME is the path of executable.
This will then run the command from the server (assuming the WINNT directory resides on the C: on the server).
Lee.
Reply to this topic
0 user(s) are reading this topic
0 members, 0 guests, 0 anonymous users
Click the link below to see the new game I'm developing!
