Here is the process that I am following:

I run START32 in the CREATE Event of the Window. I run STOP32 in the CLOSE Event of the Window. A Button on the window runs a single page print preview. If I run the window and click the button, the print preview "usually" appears. 15% of the time I have to click on the button twice for the print preview to work. The remaining 85% of the time, if I click on the button again after the print preview, I get the following error:

"OpenInsight Printer Interface has encountered a problem and needs to close. We are sorry for the inconvenience."

What am I doing wrong and how can I get the button working 100% of the time. It seems to me that I should be able to do multiple prints without needing to STOP32 and then START32 each and every time.

I am using OIPI 4.10 and would appreciate any assistance that I can get.

Eric,

Why would you start and stop OIPI in a window?

Normally start Oipi when OI starts and close Oipi when you exit the system.

I think the problem is a "time" problem because it is still initialising and you are already trying to print.

Maybe the user also closes the window before the printing is finished, in which case Oipi wont close immediately. Then when you try to open it again it becomes a mess.

Check in your Task Manager after you opened the Window if OIPI is loaded, then also check when the window is closed if OIPI is now not there anymore.

Hope it is not too confusing.

Gerry van Niekerk

Csoft

Eric,

What version of OpenInsight are you using? You said you are using OIPI 4.10, but perhaps you meant OpenInsight.

In OpenInsight 4.0.x through 4.1.2, you need to do one START32 when the application loads and one STOP32 when the application is closed. You can then run as many OIPI reports as you like in between. There are a few ways to approach this but the easiest way is to hang this code on the CREATE and CLOSE events of your primary application window. This assumes, of course, that the end user cannot close this window without closing the application at the same time.

OpenInsight 4.1.3 does the START32 and STOP32 automatically for you (unless you specify otherwise), which is what I think Gerry was talking about.

dbakke@srpcs.com

SRP Computer Solutions, Inc.

I am using OI 4.13 and OIPI32 does start automatically on system startup. However…. After one successful print, I get the following error when I attempt to print a second time. I have removed the START32 and STOP32 commands and the results are the same.

"OpenInsight Printer Interface has encountered a problem and needs to close. We are sorry for the inconvenience."

Can anyone help me with this?

Eric,

I don't know if I can be of any help, but do you check the status returned from your Set_Printer and Get_Printer calls? Perhaps there's an error status some time before that fatal message appears.

(I assume you already know about error status values returned by Set_Printer. If you're confused by me asking about status returned from Get_Printer: At least in the old days of 16-bit OIPI if Get_Printer had a problem it signalled that by returning the message name instead of the value it was supposed to return.)

- Oystein -

I took my 16-bit App and reloaded the updates to convert it to 32-bit and it works fine now. Go figure! No idea why the first upgrade didn't work and this one did. Thanks for the help guys.

View this thread on the Works forum...