Date for your Diary – 29th September 2015

OpenInsight 10 Login Screen

I am pleased to announce that Mike Ruane will be over from the USA for the week commencing 28th September 2015 and this will be a very special week for anyone working with OpenInsight in the EMEA region.

The week is still in the planning stage at the moment and I will be writing to my OpenInsight developers in the region shortly with more details.  However, we plan to hold our usual RUG meeting on the Tuesday morning (29th September 2015) and this will be followed by a very special OpenInsight 10 training session over the next couple of days (afternoon of the 29th and then all day on the 30th September and 1st October).

There was a mountain of information provided at the recent Revelation World Conference in Texas and I hope to share just a small overview of this information during the training sessions on offer.

The plan is therefore to hold the usual RUG meeting during the Tuesday morning, running up to lunchtime.  This will be a free to attend session and it will provide everyone with an opportunity to hear about how Revelation are doing, plans for the future, etc.  I also hope that Mike will provide us with a very brief overview of the OpenInsight 10 release.

Everyone will be welcome to have lunch with us at the conference centre and then we will change from the usual RUG schedule to begin a more in depth look at OpenInsight 10.  This afternoon session and the next two days (Wednesday and Thursday) will be given over to getting deeper into the forthcoming OpenInsight 10 release.  Both Mike and Carl will be on hand to take you through the massive changes to the API, the Presentation Layer and the Universal Driver, as well as Performance Enhancements, new System Admin Tools, etc. etc.  In addition, Mike will discuss the options for the conversion process and how you can have your data tables optimised as part of the process – getting to OpenInsight 10 is not a simple one click upgrade!!!

There will be a charge for the two and half day training session, but based on what I learned at the conference earlier this year, it will be well worth the expense and time.  If you are a professional OpenInsight developer, a professional MultiValue developer or you head up an OI or MV based development team, this is a three day event that you cannot afford to miss.

Granted, you could dive into the beta software or the full release when it is available, but the changes are wide and varied.  For example, Carl alone spoke for over four hours at the conference, covering the Form Designer and Presentation Layer changes.  Mike took the best part of three hours to run through the OpenInsight 10 overview and the conversion process and there were over 20 hours of facts, features, statistics, enhancements and more.

I therefore highly recommend that you consider this training session to make sure that you and your business is best prepared for the new version and that you can get the most from it for yourself, your business and more importantly your clients.

This is the most significant release since Revelation took OpenInsight into the 32-bit world.  Use this one time opportunity to get ahead of the game and be better prepared for this ground breaking OpenInsight release.

To register your interest in either the RUG or the training session (or both), please email  I am expecting the RUG  places to fill very quickly, so please don’t delay.

Cheat Sheet for HTML coders using O4W

Whilst the wizards in O4W can help developers and power users to build some very nice online database driven applications in super quick time and without the need to write, debug and maintain Web2.0 code, it is no surprise that the true power of O4W is held within O4W’s extensive API.  However, whilst most OpenInsight and ARev developers take to building web pages using the API like a duck takes to water, HTML coders with only a little (or no) BASIC+ knowledge might flounder and find themselves on a shallow, but still unwanted, learning curve.

It is for this reason that Bryan has put together a very, VERY, useful cheat sheet to help developers with HTML knowledge to quickly and efficiently apply that knowledge to building O4W pages using the API.  The cheat sheet is split into three key sections with each showing the HTML tag, attribute, style, etc. and the corresponding O4W API attribute (I hope that I am using the correct terminology here, but someone will correct me if not).  The three sections include:

  1. A non-exhaustive list of the HTML generated by O4W.
  2. A non-exhaustive list of the attributes and styles that O4W generates.
  3. A variety of HTML5 compliant APIs used to support both mobile and newer (HTML5) browsers.

O4W API calls generate HTML in addition to javascript, and occasionally it is useful to know which O4W call generates which HTML.  For example, when searching the internet for a particular solution to a problem, the results will usually be displayed as “regular” HTML; to convert that information into useable O4W calls, it is important to know which O4W calls will return the desired HTML.  This cheat sheet is therefore especially useful when used with the main O4W Reference Guide which documents all of the O4W API calls.  If you are familiar with HTML, then you can look-up the HTML in the left column of the table and then the sheet will give you the corresponding O4W API call to use in the right hand side column.  Armed with this information, it is then a simply task of checking the O4W Reference Guide for more detailed information about using the O4W API call.

As Bryan says, “It’s likely that at some time you’ve found yourself working in O4W, and wondered how to accomplish a specific task (like changing the borders on a table, or generating pre-formatted text).  You probably turned to Google (or your favorite other search engine) (but most likely Google) and found the answer in a few seconds – but the answer told you what HTML you need to use to generate your desired results.  How do you translate that HTML back into O4W API calls?”.  It is this cheat sheet that directly addresses this need.

OI 9.3 Beta – Basic +

Just two more postings and we’ll have covered the highlights of the OpenInsight 9.3 beta release.  Today, we will turn our attention to enhancements that have been made to Basic+.

  1. The COLDROPDOWNLIST message now repaints combo controls when they are being set.
  2. EMAIL_FORMAT now allows domains that begin with numbers.
  3. The CREATE_TABLE command will no longer append the user’s name and the ‘@’ sign when created by non-system administrators.
  4. DELETE_TABLE will now remove the bang table from the database.
  5. GET_ENV now returns values above 53.
  6. An issue where any popup would not return any value if the last popup had a system error.
  7. RTI_REMOVE_INDEX has been created to remove all indexes from a table including deleting the bang table and SI.MFS.
  8. New extended math operators have been added.

The 9.3 beta readme includes more details about the above items and the remaining items that I have not noted above.  In addition, it also includes many of the new features, enhancements and fixes throughout the 9.x releases.  Please drop
me a line
if you would like to receive a copy of the full 9.3 beta readme file.

>Sending a Fax from OI’s Basic+


Back in April, I mentioned that version 9.0.1 would include a new function (RTI_SENDFAX) that provides OpenInsight developers with the ability to send a fax directly from within OpenInsight (from Basic+ to be precise) using the standard Windows Fax Server that is included in Windows XP, Vista, Server 2003 and Server 2008.

Revelation have recently released an example of how to use this new function and it is copied below.

0001 Declare Function RTI_SendFax
0002 ReceiverFax = “+44 123 4567 8910”
0003 ReceiverName = “Bill Smith”
0004 Subject = “A Fax from OpenInsight’s “
0005 Subject:= “RTI_SendFax”
0006 Note = “This is a test fax” : @vm
0007 Note:= “from the” : @vm :
0008 Note:= “RTI_Sendfax command”
0009 CoverPage = “”
0010 HostFile = “”
0011 ItemName = “c:\revdotnet.txt”
0012 SenderName = “”
0013 SenderEmail =
0014 SenderFax = “01234 567891”
0015 FaxServer = “”
0016 SendFax_Status = “”
0017 JobID = RTI_SendFax(ReceiverFax, ReceiverName,
Subject, Note, CoverPage, HostFile, ItemName,
SenderName, SenderEmail, SenderFax, FaxServer,
0018 If jobId Else
0019 * Error Handling
0020 end