We are having BaaN IVC4 running on HP Unix 11.0 under Oracle 8i Database. We have developed lot of reports using Oracle Report writer 6.0. We have installed Oracle runtime files of reports and forms on the User PC's and users are accessing these report directly from the Oracle database

Now the question is, can we call these .exe files through baan sessions so that users need not to switch systems to access these reports

Can any one shed light on this ?


Regards

Create a shell script to run it from OS. Then In Baan Menu create a option to call this shell scripts. IF NT use batch files.
OR You can create a Baan session to call this script using shell function if at server or app.start() if at client.

Thanks

Jay

I can call the shell script to be run from BaaN. But the Oracle run times files for the reports & forms will be in the user PC's.

So how can i communicate between Windows & UNix ? :confused:

Any one can help ?

Regards

Oracle Developer is available for a number of platforms including HP. You could license another copy of Developer for the HP and port the reports over to run under Developer on the HP. Then you could run them from your Baan shell command. We have done this before when we had both an SGI (UNIX) server and PC's (Windows) and had licensed versions of Developer for both. You can create applications on either, and then port the application to the other with little change required to get it running under the new environment.

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)


Syntax

long app_start( string commandline, string directory, string stdin, string stdout, string stderr )

Description

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.

Arguments

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.
Notes

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.

Return values

>=0 success; identification number of the started application is returned
<0 error (that is, the negative value of the system error)

Context

ttdllbw library function.

/Claus