Year 2K - how to shake down your system

[Scott Cornell <CORNELLS@xxxxxxxxxxxxxxx>]

Ok, here's a good one for the list...most
of the Y2K tools I've seen any information
on do all kinds of cool things for IDing
programs needing changes, testing changes,
heck some even do the code changes for you.
 But I have yet to see a tool that will
tell me "OK, here are the dates in your
system - DB, displays, reports, the works."
 Most of 'em make you enter the date fields
manually, THEN they tell you the extent of
your problem.

What I did for one of our smaller in house
apps was 

- dumped out *ALL fields using DSPFFD
- killed the "obvious" non-dates (e.g. 7.5
numeric fields, 25A character fields, etc)
using SQL
- painstakingly reviewed the remaining
fields for dates (by field text and actual
contents in the DB)

I'm not thrilled with this process, either
for it's accuracy nor the amount of effort
it requires.  Anybody out there got any
better ideas on how to perform this
critical 1st step for Y2K fixing?

Scott Cornell
Mercy Information Systems
* * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * *
* This is the Midrange System Mailing List!  To submit a new message,   *
* send your mail to "MIDRANGE-L@midrange.com".  To unsubscribe from     *
* this list send email to MAJORDOMO@midrange.com and specify            *
* 'unsubscribe MIDRANGE-L' in the body of your message.  Questions      *
* should be directed to the list owner / operator: david@midrange.com   *
* * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * *