× The internal search function is temporarily non-functional. The current search engine is no longer viable and we are researching alternatives.
As a stop gap measure, we are using Google's custom search engine service.
If you know of an easy to use, open source, search engine ... please contact support@midrange.com.


  • Subject: Re: Specifying dates in DDS
  • From: "James W. Kilgore" <qappdsn@xxxxxxx>
  • Date: Tue, 17 Mar 1998 06:37:28 -0800
  • Organization: Progressive Data Systems, Inc.



neil.williams@pocruises.com wrote:

>      <<snip>>
>
>      What if;
>
>      1) The database is accessible stateside and in Europe, and each
>      location wants the dates displayed as 'native' e.g. MMDDYY stateside
>      and DDMMYY in Europe.

Date data types are as easy to convert from/to any of the formats as it can get.

>
>
>      2) There are special dates in the RPG part of the application (e.g.
>      99/99/99 and 00/00/00.

Use *HIVAL and *LOVAL respectively, gets you the same result.

>
>
>      3) We want to write 'Date Engines' for all our date
>      handling/validation, and these must comply with 1) above.

Regardless of the date storage option you are facing, I imagine you would 
convert
all incoming dates to a single format (ccyymmdd) then run the date through your
'Date Engines', see answer to 1) above.

If you are going to go through the exercise of changing your application.  Go 
the
way of the future.

My 2 cents.

+---
| 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 MIDRANGE-L-UNSUB@midrange.com.
| Questions should be directed to the list owner/operator: david@midrange.com
+---


As an Amazon Associate we earn from qualifying purchases.

This thread ...

Replies:

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

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.