Re: Trigger weirdness with L-Date fields

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?

I have a kludgy version in place, using the "after trigger/update-within-trigger" method, but given that it's an RPG program, that strategy has the side effect of putting "attempted to call RPG program recursively" messages into the Joblog.

So if there's any chance of getting the original strategy of pre-modifying the update working (or failing that, at least keeping the joblog clean), it's certainly preferable.

It's on a v6 box. And it's a dozen L-Date fields, and every one of them is complaining, without any of them being touched by the pre-modify code, regardless of what's in them.

--
JHHL