Upgrading REVG to something else (RevG Specific)
At 22 JAN 2004 03:25:44PM Jude Bell wrote:
If one is being pressured to "modernize" one's REVG database, which has been serving satisfactorily for nearly 20 years, what is the best way to go? To AREV? To MS A***ss? I am not a developer, but I have been able through the years satisfactorily to alter and add to the program. But the DOS-illiterates want a fancier and perhaps (to them) easier interface.
At 22 JAN 2004 05:26PM Donald Bakke wrote:
Jude,
Well a whole lot could be said to help in this. As a very quick and brief response:
1. Moving to AREV is a lateral (albeit better) move into another DOS system. So that might not help if the perceived need is for GUI.
2. Access isn't anything I would wish upon my worst enemies.
3. If you are seriously looking at a GUI migration, the best route would be to go to OpenInsight which is Revelation's Windows development environment. It still supports the much beloved multi-valued and variable length fields. It will be much easier to port the business logic and data files into OpenInsight than anything else.
4. There are several companies that frequent this website who can assist you with this. Best place to start looking is in the Developer's Network link on the left side of this page. I don't mind saying that we are one of those companies that are available.
Best wishes in this!
dbakke@srpcs.com
At 22 JAN 2004 06:47PM Wilhelm Schmitt wrote:
Jude,
as an add-on to Don's message:
If you have to prepare for a GUI + WAN + multiplatform environment with heavy workload you might also want to take a look at JOI, which bundles OpenInsight on the server side, a thin Java client and XML for data transfer.
Most of our Basic+ routines running on the server don't really differ much from those written in ARev or RevG, because the visual part is done in the java client.
Wilhelm
At 23 JAN 2004 03:07AM dsig@sigafoos.org wrote:
and to follow onto Dons message ..
I am just guessing here, not knowing the size of your system etc, but my guess is that whatever you do OI will be the easiest of any port. Back in the good old days of RevG developers really knew how to use (abuse too) the MV environment. So you will have Fields, multi-values and sub-values (i have even seen older systems where the developer, being a 'Da Vinci' kind a guy had added sub structures to sub-values oh my
The data structure will be the same from RevG to OI (meaning you can copy data from a RevG table to a OI table). The Dicts will need to be changed but that is not too big a deal (depending on your dicts).
The UI will be the biggest amount of work. And although I am sure there are those here who have some 'screen scraping' routine for G to OI you might just want to do it from scratch.
But I feel you pain. Change for Change sake is a pain. And seeing systems, like yours, that work day in and day out be replaced 'cause' really frosts my flakes But as a developer .. wahoo .. more work
Keep the questions coming
dsig@sigafoos.org
Phone: 971-570-2005
OS: WinXP Pro
OI: 7.0
At 23 JAN 2004 05:06PM Warren wrote:
Upgrading to OI would allow you to keep most of your database structure intact so long as been pointed out that the developer pretty much played withing the MV rules.
If all you entry screens are developed using RDesign and not a custom entry system then I would consider going through Revelation's porting lab which will convert your database and a good percentage of your entry screens to OI.
Contact Revelation for details.