Re: Y3K or not to Y3K

Based on what you have described so far I don't think you should change
to 8 digit dates.  If you are going to change anything it should be to a
True date type.  If not then leave it at 6 digits.  If there are no
prior dates to worry about then 8 digits gives you nothing over 6. 
However Date type will give you access to date processing directly in
SQL, ODBC etc.  

The question is when will this be a benefit to your client.  I think it
is a given that at some point the data will need to interact with other
computer systems.

John Hall
Home Sales Co.

boothm@earth.Goddard.edu wrote:
> 
> "Evilness"?  No, not evilness.  And no, I wasn't trolling.   This client
> just bought a new AS/400 and installed his Sys/36 software on it in the
> M36 virtual machine with SSP.   He gets very evasive when I mention
> migrating to native AS/400.  His setup has been running with almost no
> changes for 15 years, and he has no desire to change now.  The software is
> particularly robust and not at all brittle;  I have to admit I admire the
> programs that were written for him in the 1980s.  The stuff works and on
> the new AS/400 this system absolutely flies.
> 
> I am fighting a battle in  my mind of my responsibility to the client.  He
> wants durable software, cheap, with no great changes in his set up.  So,
> do I match into his existing stuff, or "force" him to the 21st century
> against his will?
> _______________________
> Booth Martin
> boothm@earth.goddard.edu
> http://www.spy.net/~booth
> _______________________
>
+---
| This is the RPG/400 Mailing List!
| To submit a new message, send your mail to RPG400-L@midrange.com.
| To subscribe to this list send email to RPG400-L-SUB@midrange.com.
| To unsubscribe from this list send email to RPG400-L-UNSUB@midrange.com.
| Questions should be directed to the list owner/operator: david@midrange.com
+---