Re: Y2K Blowup - ADK

[Lisa Abney <abney@xxxxxxxxxx>]

Thanks to all for the %NOD suggestions ... as it turns out, I owe an apology to
poor old AS/SET for assuming it was the root of my problems.  Sometime late last
fall we installed a third party software package (that shall remain nameless,
but was a European package) and (very coincidently, I'm sure) soon after
discovered that our default date format had suddenly switched from MM/DD/YY to
DD/MM/YY!  Surprisingly, we've only had this bite us a couple times, always with
UDATE, which %NOD apparently uses.  One of my programmers worked some magic
today and was able to correct it ... sure is scarry where this might pop up
again!  However, I'm scared to death to change the default back to MM/DD/YY ...
any thoughts or opinions?

CompTech Solutions, Inc. wrote:

> On eariler versions of AS/SET when you convert the %NOD back to a date with
> %CTD, it dropped the 2 century digits when going to an 8,0 field.  This has
> been corrected.  What version of AS/SET are you on?
>
> -----Original Message-----
> From: Lisa Abney <abney@iquest.net>
> To: BPCS-L@midrange.com <BPCS-L@midrange.com>
> Date: Saturday, January 16, 1999 4:30 PM
> Subject: Re: Y2K Blowup - ADK
>
> >Speaking of ADK (ASSET) ... we have a custom-written ADK program that uses
> %NOD
> >(number of days since beginning of century) that has started giving really
> strange
> >results since 1/1/99.  Anyone else seen anything like that?  I have to
> think it's
> >Y2K related, but haven't figured out why.
> >
> >Ata510@aol.com wrote:
> >
> >> And just one more word of caution to add to all of this Y2K talk. Those
> of you
> >> using ADK (ASSET) for writing applications, and who used ADK date
> routines
> >> should be careful to get 6.004 ADK, and recompile any programs that used
> date
> >> functions. There is even 1 Y2K BMR that recently was input for this ADK
> >> release (for EDATE function). 6.004 ADK is the ONLY Y2K compliant version
> of
> >> that product. But - at least upgrades are free.
> >>
> >> Thanks
> >> +---
> >> | This is the BPCS Users Mailing List!
> >> | To submit a new message, send your mail to BPCS-L@midrange.com.
> >> | To subscribe to this list send email to BPCS-L-SUB@midrange.com.
> >> | To unsubscribe from this list send email to BPCS-L-UNSUB@midrange.com.
> >> | Questions should be directed to the list owner: dasmussen@aol.com
> >> +---
> >
> >
> >
> >+---
> >| This is the BPCS Users Mailing List!
> >| To submit a new message, send your mail to BPCS-L@midrange.com.
> >| To subscribe to this list send email to BPCS-L-SUB@midrange.com.
> >| To unsubscribe from this list send email to BPCS-L-UNSUB@midrange.com.
> >| Questions should be directed to the list owner: dasmussen@aol.com
> >+---
> >
>
> +---
> | This is the BPCS Users Mailing List!
> | To submit a new message, send your mail to BPCS-L@midrange.com.
> | To subscribe to this list send email to BPCS-L-SUB@midrange.com.
> | To unsubscribe from this list send email to BPCS-L-UNSUB@midrange.com.
> | Questions should be directed to the list owner: dasmussen@aol.com
> +---



+---
| This is the BPCS Users Mailing List!
| To submit a new message, send your mail to BPCS-L@midrange.com.
| To subscribe to this list send email to BPCS-L-SUB@midrange.com.
| To unsubscribe from this list send email to BPCS-L-UNSUB@midrange.com.
| Questions should be directed to the list owner: dasmussen@aol.com
+---