Showing posts with label ARev. Show all posts
Showing posts with label ARev. Show all posts

Thursday, 28 October 2010

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.

Friday, 6 November 2009

From the desk of Bill Caisley



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?