My apology, Calvin, if I seem to be harping on this...

The code is in the Init - startup of the form. Right?

So if it issues the alert, indicating a bad record count, then the record count has got to have been mis-set some time before, right? (it is wrong at startup of the form, before any writing is done BY THIS FORM)

So the real "culprit" here is the operation that causes the incorrect record count in the first place.

For the table(s) in question, is ALL update/new activity done under TRANSACTION control? If so, then it would seem legit to suspect only something related to TRANSACTION processing itself. If not, then the real "culprit" could be anywhere.

My feeling is that this needs to be found and fixed andthat it is the finding of the thing that distorts the record count in the first place that is the key.

cheers

>No, I put this code in the init of sensitive screens PRIOR to adding any blank records. Something like this 'if tablecheck('table1'+tablecheck('table2') < 2 Alert User'. I have been fighting this for about 18 months and still do not know how to prevent this situation from occuring. It is probably caused by the convergence of a full moon, an electrical surge, and a slightly damaged DLL deep in the inner working of one of the many varient versions of Windows.