Larry,
The old "random record deleting" problem, in my experience, is usually a certain sequence of events, that was not considered, that leaves the wrong table selected prior to a DELETE command. Check your code for instances where a new record addition is canceled, and deleted.
Mark
>Here's a good one. I've got an client running an application written in FPW2.6 and currently there are several transactions in a transaction file which delete themselves. This manifests itself by:
>
>1. Client runs report for all transactions in, say November
>Report balances nicely. Everything is fine.
>
>2. Client runs same report 3 days later. for November
>Report shows out of balance transactions. Searching for these shows that they are missing.
>
>3. Client calls me, their friendly support guru
>
>I go into the raw transaction files and find the transactions marked deleted. Also, any RELATED transactions are deleted as well. (The way this works in this app is that there are "subtransactions" which are components of a main transaction (it is a fund accounting program). These are all related through a common key field.
>
>We have ruled out human error. (no really...) It happens randomly.
>The application has worked fine for *years*. This only started happening in the past month or two.
>
>Need ideas! Thanks.
>
>Best wishes,
>
>--- -Larry
"It hit an iceberg and it sank. Get over it."
Robert Ballard, dicoverer of the Titanic wreckage.