I have a problem similar to Paul's "On prepare change exception not
being raised" that has nailed us twice that we know of
in the past 20 days ( and cost us in fines from the government -
that is how we found them).

Apparently there is an error occuring on tIBOTable.POST and no
exception is being thrown (the except from the Try ... Except never
gets triggered). Then in the next iteration of the loop some of the
old data gets posted to the ID of the next company though the loop.

IE (explicit start and commits used at the database level)

Company 1:
Record 1 values get entered into the fields - no exception raised.

Post attempted. - no exception raised.

(other related query appends either not processed or failed due to
integrity on this record - no exception raised in any case)

Company 2:
Record 2 ID, acount numbers, government agency, etc get entered
into the record. Dollar amount from record 1 is still in the amount
field even after the new amount is "assigned". IE: FIELD rejects new
input but doesn't raise an exception.

No errors generated. So, post made - successfully.

(related appends generated on this id)

Company 3:
Record 3 all value entered correctly, post correctly.



The data now has:

NO trace of record 1.

Record 2 with the amount from company 1.

Record 3 correct values.


Every attempt to duplicate it with the same records on the restored
previous nights DB failed to produce the error (indicating DB
structures after a restore being cleaner may play a part).

Issue 1 is the lack of an exception that can be trapped by the
except clause during the first record's input.

Issue 2 is the mixed data from different records (some fields not
taking the new data after whatever error occurred) being used in the
following append.

This resulted in taxes from one company being reported to a state
for a different company which had never done business in that state.


Thanks for you help. I hope you can find the culprit that is eating
the missing exceptions.

Version 4.2Hj