Paradox v4.0 & 3.5 Y2k Timebombs 2

[Alt255]

My current assignment includes the inspection and correction of nearly 500,000 lines of Paradox script. The previous programmer must have assumed that 1999 was the end of time (he did most of his date math based on that assumption). I've been searching the network for strings, such as, "-1900", "99" and so forth and have already corrected dozens of "company killers". Is there an easiler way? Is there a commercial product that can identify funky date math and non-compliant date string concatenations in SC, BAS and PAS files?<br>
<br>

 

[virgo]

There are a number of things available. However, these assume a consistent name for all dates that are in the program. And, name, format, and type must be consistent.<br>
<br>
I have never been in a work environment where all of the above were met. Even when I have been able to use a tool of some sort, I had to do a lot of 'prowling' through the code.

 

[Alt255]

Thanks. I wrote an app in Visual Basic that tears apart the tables, checks the links in reports and forms and scans the scripts for funky date conversions (strval(year()-1900), etc.). It seems to work pretty well.<br>
Probably more work than it was worth, since we're thinking about ways to scrap Paradox.<br>
But until 03/01/00.... :-0