>Weird Behavior #1
>This occured on a single machine running Windows 98SE. A payment was posted. The program posted 7 transactions to the wrong account and then 6 to the correct account. The first transaction posted to the wrong account was for an odd amount, less than the regular amount, and the next 6 were for a regular payment. All six postings to the correct account were for the payment amount. A receipt was printed for each posting. The receipts are timestamped approx 10-15 seconds apart. The incorrect account is the first record in the customer table. The program is written in VFP7 SP1.

Calvin, this could be a corrupted index. Try pack the file and/or reindex it. Make a copy before you start.


>
>Weird Behavior #2
>This occured on a production program which is being run on approx 100 client sites. This behavior has not been reported any where else. There is a line of code :"Set order to tag recnum". (I know recnum is a reserved word but this was a conversion from a Clarion program and I used the same file structures and names and besides it never gave me a problem.). In any case, on this machine the program reports an error subsequent to this line - "No index tag set". There are several other places in the program with this exact same line and there are no problems in execution at those points. I have changed the index to recnums, but how come this works on 99 machines and not on this 1???

Make sure that (a) the index file exists and (b) that the tag "recnum" exists.