Re: Trigger weirdness with L-Date fields -- MIDRANGE-L

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

I use date fields all the time...

Some things to check...

- Make sure CVTOPT(*DATETIME) is NOT being specified during the compile
- DATFMT specified in the h-spec and in the DDS of the file.

I've never had a problem, but my DATFMT is always *ISO. I suspect
having something else specified is trickier.

Charles

On Tue, Aug 23, 2011 at 5:59 PM, James Lampert <jamesl@xxxxxxxxxxxxxxxxx> wrote:

We are attempting to use the "before trigger/Allow Repeated Change"
method of pre-modifying updates to a file that has L-Date fields. And
we're getting data mapping errors on every damned L-Date field in the
file, even if no change is made to the buffer.

Anybody else have any experience with this sort of weirdness?

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

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.