Category: ARev


Revelation Software are now very close to releasing OpenInsight 9.3.1 and please watch this blog for further news about the release over the next few days.

Although this is a point release that follows the main recent 9.3 release, this new version features the usual enhancements and fixes and a brand new data connector that will enable MultiValue developers to interface OpenInsight with Ladybridge’s QM database.  Already well tested during the beta cycle, this new connector will feature in a new commercial solution from Stage7 – watch out for more news on that right here and as it breaks.

As well as the QM connector, this new release sees 8 customer lead enhancements to the Banded Report Writer, 15 enhancements to O4W including support for ad hoc reporting, rss maintenance, mobile features (including a separate graphing library, run report function for mobile reports, etc) and much more.  The release also sees some fixes for ARev32, OpenInsight’s .NET functionality, fixes requested by you through the suggestions and bug tracker on revelation.com and work on the BFS / Connectors.

Those of you who are WORKS members will be able to download, review the full readme detailing the changes and take advantage of this new release very soon.  Please contact me if you are not a WORKS member and I will gladly email you a copy of the readme file so that you can see what you are missing out on and learn more about the new features that will no doubt be helpful and enhance your OpenInsight applications.

And finally we reach day nine and the last of my postings taking a look at the OpenInsight 9.3 beta release highlights.  Today we will take a look at what the new release has in store for our ARev clients that are making (or planning on making) the move to ARev32.  The readme includes five modifications and they include:

  1. Case options now work correctly on selects.
  2. Environment ini files have been enhanced to allow for user environments.
  3. Selecting with parentheses in the selection criteria no longer causes the select to cancel.
  4. ARev32 and CTO configuration records have been enhanced to conform to the CFG_XXX format.
  5. An additional AREV32/CTO configuration option has been included.  Setting field 6 to “<<NONE>>” will suppress the auto-start of ARev32 in AREV32_xxx_FORM (for graphical debugging.
  6. V23 (AREV32 RUN) has also been updated to save the stack when running in graphical debugging mode.

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.

There are a few instances reported that if utilising ARev tables in OI ‘I have to maintain my indexes in ARev, OI does not work!’

If you are using/attaching legacy tables from ARev in OI and there is a Quickdex.mfs on the DICT. you are unable to create a Btree on any of the fields. It will appear to have worked but the index will not exist and it will not work. If you attempt to re-add the index you will receive a message that the ‘index already exists’. What has happened is that the DICT. now has a one (1) in field six which indicates the existence of a Btree on that field.

Revelation are going to produce a meaningful error message in a future release to warn you of this problem.

To successfully maintain indexes from OI you must first remove the Quickdex.mfs from the DICT. by means of a SET_MFS. You should also edit the row in the Dict and remove the one (1) in field 6 if you previously attempted to create an index.

Please also note that Sprezzatura have begun a blog thread regarding ‘Indexing in OpenInsight – Part 1 –What is indexing?

Follow

Get every new post delivered to your Inbox.

Join 67 other followers