OIPI VSPRINTER2 (OIPI.Net)
At 21 JUL 2011 03:16:06PM Mary Jean Blink wrote:
Are the STARTOVERLAY / ENDOVERLAY messages for SET_PRINTER no longer supported with VSPRINTER2? I am unable to get them working with VSPRINTER2, but they seem to work fine with VSPRINTER.
Is anyone using VSPRINTER2 with great success? We continue to encounter obstacles and need to decide if we should just move back to VSPRINTER.
At 27 JUL 2011 08:18AM Chris Meyer wrote:
I have gone back to OIPI a while ago. Issues include .NET startup, font incompatabilities, textxy differences. I have many complicated forms and did not want to redesign them. Tried to use setprinter2 along with setprinter1 without success.
At 27 JUL 2011 09:07AM Sean FitzSimons wrote:
Mary Jean,
Chris is correct in that there are a number of issues with forms and the differences between OIPI and OIPI.NET. There were always issues with positions and font sizes and kernelling, etc., in OIPI. The Component One controls used in OIPI were optimized by Component One in their .Net control. I have found that in reports that rely heaviliy on overlays and tablecell messages and position placement should be run using OIPI and not OIPI.Net, while other reports that are text and table heavy without much special formatting work fine with OIPI.Net.
Sean
At 27 JUL 2011 10:05AM Bill North wrote:
Hi Mary Jean,
We are in the process of moving our application to OI 9.2.1 and are having problems with both VSPRINTER and VSPRINTER2, so going back to OIPI may not be an option? Aside from the formatting issues, in OI 9.2.1 using VSPRINTER some of our reports no longer run, all reports will run using VSPRINTER2 but take 2 to 3 times longer to complete.
Bill
At 27 JUL 2011 03:32PM Bob Orsini wrote:
Bill
There really should be no issues with running OIPI in 9.2.1. What do you mean by will not run at all.
At 27 JUL 2011 03:58PM Bill North wrote:
Bob,
The same report using VSPRINTER2 will run and not run using VSPRINTER, OI hangs.
At 27 JUL 2011 04:37PM Bob Orsini wrote:
Bill, if you want give me a call at and we can discuss. Never heard of a report that works in .net and not in OIPI. The only reason OIPI would hang is with an old PDF issue. 201-722-9014.
At 28 JUL 2011 06:30AM Chris Meyer wrote:
There is a known issue in 9.2.1 and OIPI. If the user closes a print preview window before the report has completed OI will crash. I believe this has been fixed in 9.3.
Again, I wish we could get updates / bug fixes more often rather than having to wait for the next release usually at conference time. I propose that developers should get regular updates, say every4-6 weeks just like many other software suppliers.
At 08 AUG 2011 09:41AM Mary Jean Blink wrote:
Thanks all for the input. Maybe I missed it, but can someone from Revelation confirm that STARTOVERLAY / ENDOVERLAY are no longer supported in the .NET version of OIPI? Was this intended or oversight? Will these commands be replaced in a future release?
Thanks!
mjb
At 09 AUG 2011 02:36PM Bob Orsini wrote:
The overlay options are not available in the controls used for OIPI.net. Also the crashing of OIPI has been fixed in 9.3.
At 10 AUG 2011 03:14PM Mary Jean Blink wrote:
Bob,
Will there be an altnerative to this in future OIPI.net?
Do you know the status of the Footer issues iwth OIPI.net? WIll this be fixed in 9.3 too?
mjb
At 10 AUG 2011 04:24PM bshumsky wrote:
Bob,
Will there be an altnerative to this in future OIPI.net?
Do you know the status of the Footer issues iwth OIPI.net? WIll this be fixed in 9.3 too?
mjb
Do you have a small sample routine that illustrates how it's supposed to work, and an example of the output as it's supposed to look? I can take a look and see if there's any way to get that functionality back (as Bob stated, it's not supported in the underlying control, but maybe there's a way to emulate it).
Thanks,
- Bryan Shumsky
At 10 AUG 2011 04:45PM Mary Jean Blink wrote:
Bryan,
Thanks you! I'll put something together and email it to you.
Since the footer doesn't work properly in the OIPI.net version, we want to use the Overlays to handle footers.
And, while the headers do position correctly, we want a more sophisticated header (i.e. a table using ADDTABLE, etc.) that will print on each page. We may also want to do a different first page header from the rest of the report.
In the footer, using overlays we can determine the total number of pages and print a nice footer with Page # of ##.
Overlays get added to the report after the base report is completed. You can overlay any OIPI command to any page you want. It was quite cool!
Thanks again!
Mary Jean