Hello to all,

I am looking for some guidance in performing a long overdue upgrade to our Arev system. We are currently running a 30-user version of 2.12 on a Novell 3.x network W/ the Arev NLM. I am upgrading our main system and 30+ applications to 3.12 so that we can eventually share the data with OpenInsight.

I have quite an assortment of disks on my desk to use in the upgrade process. I have a 3.0 upgrade with supplemental disk, 3.01 maintenance release, 3.03 maintenance release, 3.1 upgrade, and the 3.12 maintenance release.

And now for my questions?

Can I perform the full 2.12 - 3.12 upgrade to the Sysprog account, and then perform all of the batch updates to the individual application tables? Or, should the apps be upgraded after the 3.03 step and then again after the 3.1 upgrade?

I have been experimenting on a spare file server with varying degrees of success.

During all attempts, when it comes time to update application tables, I receive the message that no tables need to be upgraded. I would think otherwise??? I may have seen a posting here about this issue so I will do some more searching on that.

While installing the 3.12 maintenance release, I received the error message that Arev could not locate DICT.SYSMENUS. Performing a LISTVOL confirmed this. I then checked our production 2.12 system and did not find a DICT.SYS.MENUS there either. Did I loose my dict? I experimented by copying DICT.MENUS to DICT.SYSMENUS and the upgrade seemed fine. I am a bit leery of this fix though.

All help/advice/direction will be GREATLY appreciated.

Todd Meuth - Illinois State Lottery

Todd, when you purchase a 3.12 AREV direct from Revelation Software, you get a 3.10 release and a set of 3.12 upgrade disks.

So your answer is that the following sequence applies

2.12,3.0,3.10,3.12

Your dict.sysmenus recovery was entirely appropriate.

Remember to have thorough backups (even a zip file in situ will suffice) ahead of any upgrade.

Sometimes the 3.12 upgrade does not work first time and you have to repeat it to get it to "stick".

Steve

Todd

In addition to Steve's advice ensure that each account/application only has one VOC file. It is quite possible in Arev 2.x to have a VOC on Revboot and another in a programs directory which gets attached at logon and becomes the active VOC. If this is the case, copy all records from the active VOC to the original one (you'll need to set and alias) and then delete the one on programs directory.

The reason for this is that whilst 3.x upgrade prompts for location of the accounts VOC we have found problems in trying to upgrade clients applications in this way. Far easier to just have one.

We also tend to remove indexes and then recreate then in new 3.12 version - may be overkill but it removes any possible problems especially if you 2.x app has itself been upgraded from 1.x

Finally check some windows with paint where there are amv groups as some may need to be re-saved to prevent wierd scrolling, especially if amv group are the last prompts on page.

Tony

View this thread on the forum...