|
Good idea Scott. And, providing your applications do not directly access the physical file, but only access the logical files, you could add fields without any level checks. I've seen this technique used by a software vendor. Instead of selecting all fields in their logical files they only selected the fields previously used in that logical file. To change from an 6 digit date to either an 8 digit date, or a true date field, then the field in the logical file could do one of two things: 1) Be mapped over a conversion of this field back to 6 digit, via a UDF or some other technique. In this case your physical would only have one date field. 2) Have a trigger program update the 6 digit date field every time the true date field was manipulated. In this case your physical would have two date fields, kept in sync. Rob Berendt -- "They that can give up essential liberty to obtain a little temporary safety deserve neither liberty nor safety." Benjamin Franklin "Scott Johnson" <sjohnson@xxxxxxxxxxxxx> Sent by: midrange-l-bounces@xxxxxxxxxxxx 08/12/2003 03:02 PM Please respond to Midrange Systems Technical Discussion To: "'Midrange Systems Technical Discussion'" <midrange-l@xxxxxxxxxxxx> cc: Fax to: Subject: RE: SQL date comparison - a better way? Get with at least the 90's and update the fields to Date Data Types. ;-) Just couldn't resist. What you have looks good for what you need to do. Do you really have dates before 1940? If not you could get rid of that part. Like somebody else suggested, you may want to look into user defined functions. Just depends how often you plan on running this statement. -- Scott > _______________________________________________ This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing list To post a message email: MIDRANGE-L@xxxxxxxxxxxx To subscribe, unsubscribe, or change list options, visit: http://lists.midrange.com/mailman/listinfo/midrange-l or email: MIDRANGE-L-request@xxxxxxxxxxxx Before posting, please take a moment to review the archives at http://archive.midrange.com/midrange-l.
As an Amazon Associate we earn from qualifying purchases.
This mailing list archive is Copyright 1997-2024 by midrange.com and David Gibbs as a compilation work. Use of the archive is restricted to research of a business or technical nature. Any other uses are prohibited. Full details are available on our policy page. If you have questions about this, please contact [javascript protected email address].
Operating expenses for this site are earned using the Amazon Associate program and Google Adsense.