I have a client using a real estate application written in Rev G. He wants me to make sure it is year 2000 compliant. Does anyone have any experience with this? I'm also having a tough time getting behind the screens. Any hints?

He is also curious to find out if there is a third party accounts payable package he can integrate with.

Thanks.

Nannette

We have done a few Rev/Arev Y2K compliance checks. Very much depends on how the system has been written and the only way to check fully is to examine the code.

For example are dates stored as internal dates or character strings such as 010198 etc.

Can you access TCL in the Rev G application ? This is the starting point to get behind windows using RDES and dictionaries using BUD functions.

Let me know if you need more assistance.

Tony

Do you have any idea who wrote the software. Screens could

be built usign Rdesign or true basic code, depends on how it

was designed.

As far as an A/P system is concerned, I doubt there are many

packages left that are revg2b compatible, you might be able to

find an existing arev var that began in the g2 environment.

Revelation use to publish the software applications directory

and I have copies from 89/90/91 time frame

We have just been through a major exercise with our Payroll/HR package. RevG in itself is not a problem - rather it is in the design and programming of the application.

We did write a new version of RTP26 (ICONV) so that all dates with a one or two digiit year would default to a sensible centuy. We used the 80/20 rule floating on the current century.

ie. in 1998, 18-99 becomes 1918-1999 and 0-18 becomes 2000-2018. This works better for us than standard RevG.

Chris Vaughan referenced rewriting RPT26. Where could I find the source code for RPT26?

Thanks – Martin

He was referring to a rewrite from scratch. The source code is not in the public domain.

amcauley@sprezzatura.com

Sprezzatura Ltd

World Leaders in all things RevSoft

View this thread on the forum...