Is there a copy of OIPI included with OI 32? Or how do I get one? I've had some real fits trying to do reporting and dealing with proportional fonts. Unfortunately I don't think my client will spring for OIPI if it's an add-on product. Is there a workaround for the proportional stuff? Or a specific font that's Not proportional?

Also, Reporter isn't being very cooperative either.. I can't even test-run my reports without it blowing up. Anyone else having so much fun??

Give me Arev.. sigh..

Michael-

OIPI is bundled with OI versions 3.7.5 and above.

Thanks-

Mike Ruane

Michael,

I want to add that using the OIPI will easily help you control your proportional font issues. It has some very good methods that allow you to control where the text should go, whether it is right justified, requires word-wrapping within a defined region, etc. AREV is definitely in a class by itself, but OI is really a sweet product to work with…especially with the latest 4.1 enhancements coming real soon now.

[email protected]

SRP Computer Solutions, Inc.

Thanks guys! We went ahead and got OIPI.. It's sure better than the standard OI print interface. However, when I run my app, I get an error msg that says:

ENG0805: SET_PRINTER, line 192. Function GetNextWindow does not exist in dynamic link library USER32.

At this point, OI is hosed, and I have to restart OI completely.

Any thoughts?

Michael,

There were a few reasons why this error came up. One way that seemed to fix most instances was provided by Richard Bright on the Works site. Here's his original response:

I suspect that the problem is that the line in DLL_OIPI_USER32 incorrectly reads -

***]] HANDLE STDCALL GetNextWindow(HANDLE,UINT) SRP Computer Solutions, Inc.[/url]

Mike,

The CD that we got recently was version 3.7.2. How can we get a copy of the latest version?

Thanks,

Baxter

Baxter,

The latest CD that we have is OpenInsight 3.7.2. The upgrades to 3.7.5 are in the WORKS Downloads section of the web site. You will need to upgrade from 3.7.2 to 3.7.3 to 3.7.4 to 3.7.5.

Sean

P.S. I sent you an email regarding OI 4.0.2 and OIPI 4.1.

Sean,

Thanks!

Baxter

Lest someone at a later time take this (thread) to be a definitive response, please be cautioned that the suggestion - to alias GetWindow - was a work-round to solve a presumed problem with OIPI in the period when OI16 and OI32 were co-existing. In the OI 32bit code at Oi v4.0x, OIPI appeared to make a call to GetNextWindow (a WinAPI 16 bit function which does not exist in 32bit WinAPI).

With OI v4.1 I found that the alias GetNextWindow caused problems. Specifically the new Table Builder workspace introduced in OI 4.1 makes calls to initialise OIPI. The call fails on GetNextWindow. However if we retrace our steps and remove fom DLL_USER32 or DLL_OIPI_USER32 the prototypes aliasing GetNextWindow and replace with the correct form GetWindow, then all is sweat.

Richard Bright

BrightIdeas New Zealand

Richard-

This may be a remnant of one of the betas where we were rolling out OIPI Unicode changes that ultimately failed. We rolled out a new User32, and then rolled out the restored OIPI_user32, but never re-rolled out the old User32. This is being addressed.

For the record, for release 4.1, GetNextWindow should be prototyped in DLL_OIPI_USER32.

Thanks-

Mike

Noted. Sorry if I have muddied the water.

Down here we speculated at length about the alternate use of GetWindow v GetNextWindow in the context of OIPI.

Out of interest, why retain the call to GetNextWindow in OI32? I guess a good rationale would be protecting developer legacy code.

Richard Bright

View this thread on the forum...