I have an OIPI batch print routine which breaks up the number of documents into batches (each batch is its own print job) upon the change of a specific value in each record (this means the batches will be dynamically sized). The main routine does the selecting, initiates the print job and handles the batching. I use a subroutine to actually format and print each page.

I am running into a couple of problems and have implemented a couple of solutions, but am not seeing any differences.

Problem # 1.

A .bmp logo is coded to print in the upper left hand corner of each page (not set to repeat, since we print a blank page in-between batches). This prints for a variable number of pages each time the program runs and then stops printing for the remainder of the program.

Attempt #1:

a. Verified error handling. I thought maybe it wasn't succesfully initiating the print job, so I have it give an error msg and then die if it returns < 1 from the "INIT" message. Same thing for the "BMP" message. Have received no error messages, yet BMP continues to drop off.

b. Changed .bmp file to Read-only.

c. Changed formatting of bmp so it prints within the margins (was originally set at pos 0,0)

Problem #2.

Intermittently, the print job will terminate with error messages of varying types (seems mostly like Windows msgs according to what my users are telling me). Of course, this only seems to happen when they set the job to print overnight.

a. Originally limited the selection to 1000 records; this didn't seem to make any difference so it was increased to 2500. Would ultimately like the program to print all of the documents at once.

b. Coded in a proportionally-timed hold before intializing the next print job (thinking that the jobs were backing up, thus giving it time to print).

Specs are: OI 3.7.4 with OIPI 4.1 (not pro) Win 98 SE machine.

Any suggestions?

Thanks

Chip Fichot

CreditMaster

Chip,

If I understand you correctly, it sounds as if you are INIT-ing your printer and TERM-ing it after each batch print. If that is the case, try doing just one INIT at the beginning of your batches, and one TERM once printing is complete. When printing multiple jobs in a row like you are, we've seen times where the multiple INIT/TERM causes some errors.

[email protected]

SRP Computer Solutions

Hi Chip,

Here are a few suggestions:

Problem #1: How are you printing the BMP on each page – if you are explicitly setting the PAGEBREAK, then you must call the BMP message after the PAGEBREAK on all pages that you want to print the BMP on. Is it possible that something else is printing on top of the BMP … like another blank image or rectangle?

Problem #2: Are you using a TERM with the first parameter set to 1 or 0 (default)? You might try using a 1, because that will completely remove the OIPI.EXE from memory after each report.

Also – Download the latest printer driver for Win98 from the printer manufacturer?s web site, because the 16-bit OIPI is very dependent on these drivers, and the mini-drivers that come on the Windows setup CD are not very good. This may fix both problems.

Tony

Chip, I'm having a similar problem as you in that the BMP stops printing images, intermittantly. Perhaps we can help each other work this out. my email

Hi Dave,

I think Chip was using the 16-bit version of the OIPI, and you are using the 32-bit version. I assume that you have tried using the latest version of the printer driver. If this problem is occurring in both the 16-bit and 32-bit versions of the OIPI, then there may be a problem inside the BMP logic – but this message uses very simple logic. Are you checking the return value of all BMP Set_Printer calls? With the Professional version (32-bit) of the OIPI, you can call the TERM message with a 1 after each report, and the speed should be about the same – so I suggest testing this to see if it fixes the BMP problem.

Tony

View this thread on the forum...