Re: Source Dates

[dennis.e.lovelady@xxxxxxxxxxxxx]

I understand your point about SEU handling that date properly.  However, 
keep in mind that SEU is an application that can do what it wants... and 
that no sorting by date or whatever is involved.

The difference is that the database has never been told that the field 
contains dates... and the application has.

I don't know why this would have worked for you in the past.  Back when we 
were doing preparation for Y2K... circa 1998, I did a lot of testing about 
these dates and SEU.   We discovered that applications viewed the SRCDAT 
field as just a number, and that special processing would be needed if we 
ever intended to make use of the field.  Since SEU already handles the 
date properly, though, we just made a comment about the fact, considered 
it "not a problem," and moved on.

So the point is, I've seen this issue for at least the last five years.

Dennis E. Lovelady





"Bill" <billzbubb@subdimension.com>
Sent by: midrange-l-bounces@midrange.com
01/10/2003 10:53 AM
Please respond to Midrange Systems Technical Discussion

 
        To:     "Midrange Systems Technical Discussion" 
<midrange-l@midrange.com>
        cc: 
        Subject:        Re: Source Dates

dennis.e.lovelady@accenture.com wrote:
> The SRCDAT is now and has always been a numeric field of six bytes.
> There is no date-type logic associated with it.
>
> In SQL, you could use a date function to convert this to a date-type
> field, and you'd be all set.  But I cannot see how this might have
> worked in the past.

Dennis, I am tending to agree with you, but I've used this utility a lot 
in
the past - maybe I was always skirting the faulty selection criteria
without realizing it.

I did notice that inside SEU, it handles the dates correctly.

Bill

_______________________________________________
This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing 
list
To post a message email: MIDRANGE-L@midrange.com
To subscribe, unsubscribe, or change list options,
visit: http://lists.midrange.com/mailman/listinfo.cgi/midrange-l
or email: MIDRANGE-L-request@midrange.com
Before posting, please take a moment to review the archives
at http://archive.midrange.com/midrange-l.