Its possibly to start any windows appl. on the client from within a baan session, use app_start() (remember to include the ttdllbw library function, #pragma used dll ottdllbw)
long app_start( string commandline, string directory, string stdin, string stdout, string stderr )
This starts the application specified in the commandline argument. It returns an ID for the started application. You can subsequently use this ID as the app.id argument in the app_status() function.
commandline This specifies the command that starts the application. If commandline does not include a directory path, Windows searches for the executable file in the following directories, in the order shown below:1 The directory where BW is loaded.2 The Windows system directory.3 The Windows directory.4 The directories listed in the PATH environment variable.
directory The default working directory for the application.
stdin The standard input file name.
stdout The standard output file name.
stderr The standard error file name.
If commandline specifies the name of a nonexecutable file, Windows starts the application with which the file name extension is associated. For example, if commandline is c:\temp\file.txt, and .txt is associated with the Notepad application, Windows will start Notepad. Because users can change the association of a file name extension, you cannot predict which application will start.
This functionality is not available when you specify standard input, output, and error files.
>=0 success; identification number of the started application is returned
<0 error (that is, the negative value of the system error)
ttdllbw library function.