• Subject: Re: 2 digit YY on screens & 4 in DB -Reply
  • From: John Carr <74711.77@xxxxxxxxxxxxxx>
  • Date: Tue, 16 Sep 1997 22:57:26 -0400

Date:   9/16/97  7:49 PM

RE:     Re: 2 digit YY on screens & 4 in DB -Reply

>>What would the program's understanding of the following be?
>>(or "What did the User Intend"?)


>>In which one did I think I was entering D/M/Y 
>>Which one was M/D/Y
>>Which one was Y/M/D
>>John Carr

David Morris said;

>Are you just playing the devils advocate or do you really change date
>formats between applications?  What is the reason?  Even our
>purchased packages force us to set a single date format.  All of our
>programs use the *JOB format (defaulted from QDATFMT) to
>determine the order of a date field.  
> There is no guessing.
>David Morris                      

Yes,  I was playing the devils advocate.  From my experiences for customers.

But,  If I asked for a show of hands from the consultants who subscribe 
to this list,  who have seen different formats in different programs, 
different systems, in the SAME shop I think it would be every 
consultant in the house.  

Your right, most software packages force you to a single date format,
however if you have multple 3rd party packages in house they might
be different from each other.  And often are.

I guess what I'm saying is, without standards(Like Fred Mitchell's UK)
and the communication with the user there is a lot of "Guessing" out 

John Carr
| 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

This thread ...

Follow On AppleNews
Return to Archive home page | Return to MIDRANGE.COM home page

This mailing list archive is Copyright 1997-2019 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].