ARev32 / OI Hybrid Demo

Advanced Revelation (ARev) users often ask me what ARev32 provides them with. The short answer is a future proofed system in a world where DOS applications are feeling their age and running into problems. A move to ARev32 brings you into the 32-bit Windows world of OpenInsight, and shortly the 64-bit world.

Whilst a straight conversion leaves you with an ARev32 window that looks and feel just like it does under traditional ARev, an extended conversion can take you ‘a lot’ further.

My new ARev32 demo video (hosted on my YouTube RevSoftUK Channel) takes a quick look at ARev 3.12’s converted SAMPLES application and how it can be run within an OpenInsight MDI frame and then how you can mix GUI and ARev32 windows, including sending information between one and another.

It also takes a look at how ARev32 users can extend the flexibility of the ARev32 system by displaying two or more ARev application screens in their own ARev32 windows – effectively having a Customer screen open with a record and another for the Products record.

Click here to review the ARev32 Demo Video.

>What a novice can create with Openinsight!


Many of you have been chasing me on the completion of the OpenInsight QSG series of tutorials. As well as becoming very busy over the summer, one of the main reasons for the pause in the creation of the video series was my time away developing my own Contact Manager.

Some of you that are new to OpenInsight and also some non-Revelation MultiValue developers who have been looking at OpenInsight have asked to see what I have been able to achieve with VERY little technical knowledge, mostly using the OI WORKS technical resources. I did have a couple of hours with Aaron in the car back from London to Northampton for a couple of areas and Carl helped me with an email blast module using an existing routine. Otherwise it is all my own work, design, code, etc.

It is now in use daily, but still far from complete. I need some data validation in areas, some OIPI reports need to be created, a global search facility and the report library in general adding to. I also have a healthy wish list of more technical things for when my technical colleagues become a little less hectic on client work.

Anyway, I have created an overview video of the application and I hope that it will serve to demonstrate what can be achieved in a very short period of time and by a complete application development novice, using OpenInsight.

>New Tutorial Videos.


As many of you will have noticed, Revelation continue to extend the range of data connectors for OpenInsight. A data connector for Univision is in development and the D3 (TigerLogic) connector was a new feature in the recent 9.2 release.

Revelation US has recently released a couple of tutorial videos to accompany the D3 Connectors release. They include:

Setting up and working with the OI4D3 connector – Mike Ruane demonstrates OpenInsight’s connector technology and attaches data from TigerLogic’s D3 data server. Once the data has been attached, OpenInsight can then be used to quickly and easily create graphical or browser-based applications against a D3 database.

Creating an O4W report against a D3 database – Second in Mike’s OI4D3 connector series, this time he takes a look at using OpenInsight’s O4W Report Wizard against data from TigerLogic’s D3 data server. The O4W Report Wizard lets a user or developer create browser-based interactive reports.

>New D3 Connector tutorial video.


Revelation shall shortly be releasing yet another data connector for the MultiValue community.

This time, it is Tigerlogic’s D3 that comes under the spotlight. For those readers using D3, or wanting to use a D3 backend with OpenInsight as a front end, Mike has created and published a short demo tutorial on setting up and using the D3 connector. Click here to view mike’s video.

Protecting your sensitive OpenInsight data.

Sometime ago, Kevin Ruane wrote an article on hiding your Linear Hash data from workstations, this prevented direct access to the data inside .LK and .OV files (Revelation’s Linear Hash data files).

At the time, this was just another useful benefit afforded the Universal Driver for users running Revelation based systems. However, in more recent times we have seen many headlines of high profile individuals and organisations loosing client and other sensitive data – headlines that no organisation can afford to deal with and that often lead to lasting damage to the organisation’s reputation.

If that was not reason enough to take data privacy seriously, organisations now have requirements to protect and audit access to data and this is becoming a more and more common request. For instance, compliance with industry security standards like the PCI DSS (Payment Card Industry Data Security Standard) is now a must have for anyone handling credit card information through their online systems or otherwise.

Revelation has published an update to the original article which covers one method to prevent unauthorised access to OpenInsight’s data held inside .LK and .OV files. Working with OpenInsight 9.2+ and the Universal Driver 4.6 over a Windows 2008 Server and Windows 7 workstation environment (so nice and contemporary) this new article details how to use strict NTFS permissions to achieve peace of mind for developers and end-users alike. After all, if your users can not directly read or change .LK and .OV files, you can audit and protect access to the data using controls that are internal to your application.

The full article can be found on at

>O4W Examples Application Online.


Following my recent posting about the OpenInsight 9.2 Evaluation Edition being available, several of you have asked for the O4W Quick Start Guide application to be hosted on the web. This has now been done and you can get to the O4W examples application at

The current version includes an example of a Customer Entry Form, an Order Report and a Sales Dashboard. This provides you with the opportunity to view the application before downloading the OpenInsight 9.2 evaluation edition (or upgrade if you are a WORKS subscriber) and running through the O4W Quick Start guide yourself.

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: