We are developing our OI application using OIPI on an NT workstation and are having problems with the starting/stopping of the OIPI engine, which we don't seem to have on our other platforms. We are getting OIPI error message -5 (OIPI.exe or support files could not be found), when calling the START_OIPI32 subroutine at the beginning of our program in a test environment. Does anyone have a suggestion in how to start up the engine and then leave it running during the testing of our application. We are getting OIPI32 protection exception when starting.

This is the test code we are trying to use which is causing the errors.

Subroutine OITEST(void)

declare subroutine START_OIPI32, STOP_OIPI32

declare function get_printer, set_printer ,msg

 START_OIPI32('')

 stat=set_printer("INIT")

 stat=set_printer("TEXT","Test")

 stat=set_printer("TERM")

 STOP_OIPI32('')

end

Thanks. All help and suggestions are greatly appreciated.

Mark,

(To my knowledge there aren't functions START_OIPI32() and STOP_OIPI32() in OI. I assume they are your own, doing

stat=set_printer("START32")

stat=set_printer("STOP32")

respectively.)

Are you sure OIPI was properly installed in this workstation?

- Oystein -

You should start OIPI32 when the application launches.

The OIPI32 engine will be running for the duration of the application, and all reports can then use it.

When your application closes, then stop the OIPI32.

Problem here though, is if your app crashes, and OIPI32 is still running, then when you start it again it causes an error.

You can check for this via the ThunderForm test (or similar), but as this applies to all VB apps it is not a good test.

The START_OIPI32 and STOP_OIPI32 subroutines were installed with OIPI. They were part of the package, and they do what you have suggested.

I think this is exactly what's happening. How do you go about using OIPI in a testing environment and avoid the constant restarts?

I think I agree with Oystein.

I cannot see any subroutines for START_OIPI32 and STOPOIPI32 in SYSPROG or in the SYSPROCS or SYSOBJ files.

Colin

My apologies, gentlemen. I think we copied them from the OIPI EXAMPLES application.

View this thread on the forum...