>
>Does the form really have a private datasession?
>
>
>Try to close all tables manually. Having a private datasession should do this automatically, but who knows. Perhaps you will even get a relevant error message, why you can't close the tables.
>
>I am not sure which would be the appropriate method for this. Destroy() or QueryUnload(), probably.
>
>Hilmar.

Hilmar, I do have a private datasession on the form and it remains that way throughout the time the form is up. Also, in the Destroy I've closed out each individual table with USE IN ... code. They all close out fine. I'm left with only the blank datasession that is named 'Unknown'.

I've discovered that something goes wrong with one of the two DBC's I use when this form runs though. I know this because the maintenance procedures will close these DBC's and then open the System.dbc file as a table or copy the System.dbc to back it up, and these commands don't fire properly in the maintenance after the particular form is brought up and then brought down.

So, 'USE Data\System.dbc' will fail to call up the dbc as a table in one maintenance method. In another the 'COPY Data\SYstem.dbc to Data\Backup\System.dbc' will also fail to copy. It fails after this one form is up and then closed down. But when other forms are called up and closed down it does not fail in those spots.

Also, there are only one table and one view used inthat form from this 'System.dbc'. Those are each used in other forms that don't have this problem.

So, thanks Hilmar for consideration. THis is a pretty strange problem.

Wally