Hi Jim -

Got another problem...I think...

I am using Codebook for Mere Mortals (though I don't think this is pertinent to the situation). I've found that when I close a form using a private datasession in which I have changed some data - and FoxAudit has logged the changes - the datasession remains open after the form exits. The unknown datasession then causes various problems for me in the CBMM framework....

Explored the code in the LogUpdates() and ValidateLUParms() methods and found two statements that SETs DATASESSION TO the passed datasession. When I remove these references, the problem of the dangling datasession goes away, but so does FoxAudit's ability to log transactions.

To resolve the problem, I placed a SET DATASESSSION TO 1 at the end of the LogUpdates() method. Since the FoxAudit object no longer has a reference to the old datasession, the session closes without further incident.

Will this change cause any problems elsewhere in FoxAudit?

Rick Hawkins
Rose Valley Software Studio, Inc.