Revelation Newsletter January 2010

In Beta Testing
OpenInsight for Web (O4W) is now in beta testing and the feedback has been very positive! The O4W QUICKSTART GUIDE is completed and we are now in the process of creating a detailed Reference Guide. O4W will be included in the OpenInsight 9.2 release expected in Q2 2010.

List Command Reporting Update for Landscape Reports
Works members can download a patch for OpenInsight 9.1.0 and 9.1.1 to resolve a reporting bug that can occur if the definition of the report is too wide for landscape printing. This patch prevents the list command from going into a loop and crashing the OpenInsight engine on certain landscape reports. This patch can be retrieved from the WORKS DOWNLOAD SECTIONof our web site.

Tech Tips
Did you know...

That one of the new features of OIPI.Net is the ability to define input controls(textboxes, radio buttons, etc.) that are created on the form and allow user interaction. The additional Set_Printer messages are INPUT_TEXTBOX,INPUT_RADIOBUTTON,INPUT_CHECKBOX, andINPUT_COMBOBOX. Below is a sample code snippet:

DefaultValue = "LastName,FirstName"
toolTip = "Enter the last and first name"
xPos = 0
yPos = 3.5
posn = ""
posn<1> = xPos
posn<2> = yPos
x = Set_Printer("INPUT_TEXTBOX", DefaultValue, toolTip, posn)

Did you know...

That you can configure the use of OIPI versus OIPI.Net by application, and not just globally. Specific control records can be created in the SYSENV table to fine-tune the control of OIPI. OpenInsight first looks for:

CFG_OIPI*<dbid>*<userid>
then
CFG_OIPI*<dbid>
and lastly
CFG_OIPI

It is then possible to have users of application "ABC" using OIPI, while everyone else uses OIPI.Net or vice versa.

Field 1 of each control record should be either VSPRINTER for OIPI or VSPRINTER2for OIPI.Net