× 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.


  1.  Home
  2. MIDRANGE-L
  3. February 2006

Re: Override PF's DATFMT(*USA) using DSPF's DATFMT(*JOB) not working

On 2/8/06, Booth Martin <booth@xxxxxxxxxxxx> wrote:
>
> For a variety of other reasons you may prefer to define the field as
> 8-char long.  The primary reason is that you can end up with a
> user-unfriendly 01/01/01 on the screen, as a date field will not accept
> zeros or blanks.


Well, in this particular case, there's no way that the record providing the
date information would not have a valid, real date in it.

But, in general, for consistency's sake, I'll probably take your advice on
displaying a character or numeric field.

What happens if the date field in the database file is null-capable and *is*
null (null indicator is on)?  What would the display do with that?

- Dan

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.