9.x Quickdex and Rightdex patch

Revelation have recently announced the release of a patch to OpenInsight 9.0 and 9.1 to correct errors with Quickdexes and Rightdexes whereby duplicate keys are returned. If you’re in the WORKS program you can get the update here.

However, if you are not a WORKS member please contact your local Revelation representative for further details about obtaining this patch.

Starting OpenInsight/OpenEngine with Arguments

Over the last week or so we have had a few requests for details of the command line switches that are available when launching OpenInsight. They are actually listed in the OpenInsight help files and they can be found by searching for “Starting OpenInsight/OpenEngine with Arguments”.

However, for ease of use here are the details:

/ap – Application Name
For Example: /ap=SYSPROG

/un – User Name
For Example: /un=SYSPROG

/pw – Password
For Example: /pw=swordfish

/dv – Development mode flag
(1 = Development mode, 0 = Runtime mode).
Defaults to Runtime mode.

/sn – Server Name
see Client to Out-of-Process Engine.
For Example: /sn=dylan

/he – Hide Engine flag
1 = Hide Engine, 0 = Do Not Hide Engine.
The default value is dependent on the engine type.
Runtime Engines default to 1. Development engines default to 0.
Note: If you hide an Engine, the Debugger tool is disabled.

/hi – Hide Interface flag
1 = Hide Interface, 0 = Display Interface.
The default value is 0.
This option determines whether the OpenInsight Interface screen is displayed or hidden during execution. The OpenInsight help files provide some graphical examples.

/sm – System Monitor flag
1= Start System Monitor on startup, 0 = Do not start the System Monitor.
The default value is 0.
The System Monitor is not available in a runtime system.

/bn – Banner Display flag
1= Display Login Banner, 0 = Do not display banner.
The default value is 1.

/ca – Application Manager Caption
The caption may not contain spaces.
For Example: /ca=Local_OI.

/i – Indexer
This argument is used for OpenEngine only. This argument will start the OpenEngine as a dedicated indexer. The format for using this argument is /i appname.


Some specific examples include:

C:\RevSoft\OI32Bit>oinsight /ap=EXAMPLES /un=EXAMPLES
This command line will run the EXAMPLES application under the EXAMPLES user in runtime mode.

C:\Revsoft\Oinsight\oinsight.exe /ap=sysprog /un=sysprog /ca=local_oi /dv=1 /sn=soren
This command line will run the SYSPROG application with the user SYSPROG in developer mode. It will also set the window caption to read “OpenInsight – SYSPROG(LOCAL_OI) and a server name of SOREN. This will be listed in the OpenEngine Information under Queue Information.

C:\Revsoft\Oinsight\oengine.exe /i sysprog
This command line will run the OpenEngine Index Server with the SYSPROG database.

C:\Revsoft\Oinsight\OINSIGHT.exe /ap=examples /un=examples /hi=1
This command line is for use with runtime engines. The OpenInsight interface screen (The Application Manager IDE) is displayed by default. By setting /hi=1 the OpenInsight interface will not be displayed.

Why’s my oinsight.ini file not working????

We recently had a support enquiry because the OInsight.ini file (located under C:\Windows) was not being picked up and the developer was therefore unable to change the Application Manager buttons to display the System Editor ++, rather than the old System Editor.

I’d always understood that the OInsight.ini file that OpenInsight used for these settings and others, was the one in the Windows directory. However, from Windows Vista and Windows 7, things are no longer that simple.

As Carl enlightened me, Vista and Windows 7 implement something called virtual file redirection, which means that the ini file the OpenInsight uses is not the one in C:\Windows – when it asks for the file Windows goes and gets it from the Virtual Store instead. It is Microsoft’s way of trying to stop people using ini files – they don’t like you using the registry these days either!!

Anyway, the *real* ini file that Windows gives to OpenInsight is stored in your user settings folder something like:


If you change that ini file, then everything should be fine and OpenInsight will display the right buttons and your other preferences/settings.

For the more technical and those who want to understand all of this in more detail, the following link will be useful:


>Optimise your OI deployments!


There is a very useful discussion on the Revelation Discussion Boards at the moment with regards to Universal Driver and the use of revparam files. If you are involved with deploying application at any level, this is a posting that you’ll want to check out.


>S/List Patch for OpenInsight 9.x


My colleagues at Sprezzatura have just uncovered a small issue with S/List whilst running under OpenInsight version 9.x. With SYSENV CFG_OIPI set to VSPRINTER 2 (the OIPI.NET option in OpenInsight 9.x), the preview generated by S/List can terminate after only ‘printing’ the headings. All other direct output (printer, .csv, etc.) works fine.

With the VSPRINTER option set, everything within S/List under OpenInsight version 9.x runs fine.

The issue was traced to a piece of code that was set to do a GET_PROPERTY from VSPRINTER if the OpenInsight release is greater than OpenInsight 4.1.3. Support for the VSPRINTER2 logic has now been included via a minor change to the offending program and it is currently released in a patch – the full installation will be amended shortly.

Current S/List users (both Designer and Viewer users) can download the patch from www.sprezzatura.com

>Input controls in an OIPI report.


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, and INPUT_COMBOBOX.

Below is a sample code snippet:

0001 DefaultValue = “LastName,FirstName”
0002 toolTip = “Enter the last and first name”
0003 xPos = 0
0004 yPos = 3.5
0005 posn = “”
0006 posn<1> = xPos
0007 posn<2> = yPos
0008 x = Set_Printer(“INPUT_TEXTBOX”, DefaultValue, toolTip, posn)

In addition, did you know that you can now 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:
and lastly

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 VSPRINTER2 for OIPI.Net

>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 section of http://www.revelation.com/.