Re: Year 2K - IA bettter built here

[ConnectY2K@xxxxxxx]

 PART 2
Dean  lots of applications were done by may people not likely the same staff
as  doing the Y/2000 thing today. No  need to  mention documentation we all
 leave behind (as descriptive) to support or legacy art and creative actions

Had a short talk  with  Bill Gates  - tells me BOB is really a date not a
product.
MS xxx 97 application are truly not compliant or as IBM says  'Y2K Ready'.
 So  look for another in 98 as an upgrade to the 95 series

In a message dated 97-08-15 05:37:21 EDT, you write:

<< Subj:        Re: Year 2K - how to shake down your system
 Date:  97-08-15 05:37:21 EDT
 From:  DAsmussen@aol.com
 Sender:        mcsnet!midrange.com!midrange-l-owner@Mcs.Net
 Reply-to:      MIDRANGE-L@midrange.com
 To:    MIDRANGE-L@midrange.com
 
 Scott,
 
 In a message dated 97-08-14 18:05:46 EDT, you write:
 
 > 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?
 
 Sounds like you've actually got a solid base, but you know the application.
  I'd say take any 6, (maybe 7) or 8 digit/character field and examine it's
 manipulation.  You can narrow down your selection by eliminating any fields
 that meet these criteria, but you KNOW aren't dates (eg., Shop Order Number,
 Customer Order Number, Item Number, Customer Number, etc.).  If you know the
 application, your Y2K efforts can be greatly reduced...
 
 JMHO,  Dean Asmussen

* * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * *
* 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   *
* * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * *