Pretty much the same here.  Three months of time for 500,000 lines of
code.  This includes database changes, dictionary changes and finding
those pesky local variables.  No VPLUS though.  That saved us some time.
It was a little tedious, but it has been done for over a year now.
(YES!)  The best tool you can find is the best programmer/analyst you
can find.  Good luck.

Kevin Newman

> -----Original Message-----
> From: Dirickson Robert S (Steve) [SMTP:[log in to unmask]]
> Sent: Wednesday, February 10, 1999 4:21 PM
> To:   [log in to unmask]
> Subject:      Re: Transact and Y2k
>
> > Does anyone have tools that can be used to perform Y2k remediation
> for
> > Transact applications?
>
> Haven't heard of any. Except the obvious one, of course:
> Dictionary/3000. If
> the system is Dictionary-based, the job gets about 40 times easier. We
> just
> went through the 4-digit-year conversion last fall, and one developer
> did
> the entire conversion in about 6-7 weeks, working on other stuff at
> the same
> time. That's 12MB of Transact source, something over 100K non-blank
> non-comment lines of code. Probably 60% of the actual time was the
> tedium of
> updating the numerous VPLUS forms that include date fields. Because
> we've
> been pretty good (though not as good as we thought, it turned out)
> about
> avoiding locally-DEFINEd items in program source, updating the
> dictionary
> automatically brought 95% of the source up to date without having to
> touch
> it.
>
> Steve