>Can you point me to the whole article that you copied this text from? This really looks like where my problem might lie!
>
>Thanks,
>Lister Potter
>
>
>>I got some more information from MS Developer Support on a possible cause of the Ctrl-Z corruption problem. The scenario they descibe does not apply to our application but it may help someone else that's having the problem.
>>
>>====================
>>Start of Pasted Text
>>====================
>>It’s possible that a SQL SELECT statement embedded in a transaction can cause a chr(26) to be imbedded incorrectly in a table. Basically, the END TRANSACTION checks to see if the table needs to be extended. If so, it calls GetFileSize() to determine where to extend it from. However, GetFileSize() works from cached local information, and if someone else has added a new record between the BEGIN TRANS and END TRANS, then this error can (not necessarily will) occur.
>>The suggested workaround is to remove the SELECT statement from the transaction. Also, locking an arbitrary record in the table, any record, should cause the OS to refresh the cached file size information.
>>
>>This can be kind of subtle - say, if you have a list or grid from a SELECT statement, and issue a REQUERY()during the transaction, then the problem can appear.
>>==================
>>End of Pasted Text
>>==================

We have been using our Premier Support with MS to try and find a cause for the problem. The information was in an e-mail MS contact. I posted all the relevent portions of the e-mail. There is no article with more information. The information will probably show up in the MS Knowledge Base in the future if it is not there already.

As I receive more information on this problem, I will post it here.