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 syusprog account, and run the following command from the system monithr:

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')

Pleased see [url=http://www.revelation.com/WEBSITE/knowledge.nsf/07dbcbabb6b3e379852566f50064cf25/fb9fa2a4bb1e5ff085256aff007a8659?OpenDocument]this</a< knowledgebase article for some other tips.

Thanks-

Mike Ruane

View this thread on the Works forum...