OIPI and OI32 (OpenInsight 32-bit Specific)
At 10 MAY 2002 08:34:08AM Sedick Cloete wrote:
I have a problem running the OIPI_EXAMPLE1 from OI32. The program goes into debugger on SET_PRINTER with a fatal runtime error ENG0805 SET_PRINTER line 1. Function GetWindowTextLength does not exist in dynamic link library USER.
I have run DECLARE_FCNS "DLL_OIPI_USER" and "KERNEL", but still the same problem.
What can the problem be.
At 10 MAY 2002 10:57AM Sean FitzSimons wrote:
This is a posting from Mike Ruane from February.
Folks-
There have been a lot of posting here, and a lot of support calls regarding problems with OIPI and OI32, mostly dealing with the error
message "getwindowtextlength does not exist in dynamic length library USER.DLL."
The answers have been either one of both of the following:
1: There are local versions of the DLL prototypes.
Somehow the declare_FCNS 'dll_oipi_user' was run in the application that is having trouble starting OIPI. To clean these out, the
following commands must be run from the System Monitor:
RUN DELETE_ROW 'SYSOBJ', '$REGISTERWINDOWMESSAGE*appname'
RUN DELETE_ROW 'SYSOBJ', '$GETNEXTWINDOW*appname'
RUN DELETE_ROW 'SYSOBJ', '$GETWINDOWTEXT*appname'
RUN DELETE_ROW 'SYSOBJ', '$GETWINDOWTEXTLENGTH*appname'
Next, go into the SYSPROG account, and run the following command from the system monitor:
RUN DECLARE_FCNS 'DLL_OIPI_USER32'
2. The user is not using the START32 message.
The version of OIPI included in OI 4.0.1 is a32-bit version of OIPI. In order to start it, you should have the following command in the
CREATE event of your application's entry point window:
Call Set_Printer('START32')
You must also stop the OIPI. Put the following command in the CLOSE event of your application's entry point window:
Call Set_Printer('STOP32')
At 10 MAY 2002 11:03AM Sedick Cloete wrote:
Thanks Sean