Re: data decimal errors

[rick.baird@xxxxxxxxxxxxxxx]

Buck,

the business rules are what I decide them to be (and in this case, it's
reject the row).

I issue an error message and report explaining the situation and what to do
about it (get it fixed),  and that should be enough.

It doesn't happen very often, but when it does (these jobs are scheduled,
and several of them have to run at a specific time, in order, not
concurrently) and a program bombs and stops up the jobq, all hell breaks
loose.

I'd rather just trap for and report the error, process what I can and
continue.

thanks for the advice,

rick

--------- buck sez ---------------
In this case, what are your business rules?  Reject the whole transmission?
Reject the individual row in error?  Reject the bad value and use a
default?
How do you tell the far side that their data didn't pan out?  If you just
ignore the problems you can't very well tell your trading partner that
their
transmission was a dud.  I strongly advise an audit report/transmission
back
to the originator explaining the errors.  That way they can improve the
process on their side, and have the results they want.

Sorry for the strong emotion.  I have been doing import/conversions for 25
years and have not found any better way to handle this scenario, despite
being prodded by several layers of management and programmers to make the
process 'simpler.'  As soon as we get that mind reading interface going, we
can finally be rid of this whole 'send stuff, get an acknowledgement back'
rigamrole.
  --buck