Here is the story,

I have a container that contains, among many other objects, 6 cbos. The error was occuring when I used one of the cbo boxes, mind you, not the others. The tables used to load the cbos are all free and basically have the same type of structure. However, the box getting the error is loading from the user.dbf which is used "again","shared" when the program exits to set one field 'login' to .F..
To determine where this bug was, I inserted a line in exit.prg to print to screen at certain lines in the prg to tell me where the error was occuring. The debugger is useless in this case because I was not getting the error running as an app. I had to go all the way to the bottom of exit.prg, but the line was still printing indicating that the error was occuring after the last thread of execution in my program. ?? This means, after opening and closing user.dbf, and after releasing all objects, close tables all, blah blah blah. Also, I inserted 'set' when the cbos are loaded, and 'set' in interactive change of the cbo with the problem.(BTW. All my data sessions are private, I can't think of a reason for a default data session in any case. Default data sessions beg for disaster.) No unwanted files or tables were open according to MS. On a side note, beware if you use select SQL to load a cbo, it opens the selected table and leaves it open as well as the cursor which is exclusive. Also, yes, the project must be closed if modi stru is used or the exe can't use the dbc since it is left open by the table designer.(Why? Doesn't this add extra steps when trying to resolve issues related to structures?) Anyway, currently I've narrowed it down to the error only occuring if I open VFP and compile the project, then run the exe. If I don't recompile, no error. What's up with that?
EOV. (End of Venting)

Eric K.




>>>>I have FoxPro5.0 telling me that I have files and tables open that are not open. I have an exe that is getting errors, but when I exit out of VFP completely and run the .exe, the errors go away. With VFP open, I can check after an error and find that nothing is open. But if I do a close tables all, or just exit, the errors go away. Can this be fixed, or do I have to reinstall VFP?
>>>>
>>>>Eric K.
>>>
>>>open the Data Session window and see if anything is listed in the Default data session of if there are any Private data sessions listed as well. You can also do a *display memo* to see if any objects were declared public and are still hanging around. YOu may have some form object left over with a private DS with some tables left open.
>>
>>Also, do you get errors when you open multiple forms with private DS? Have you *set exclusive off* and *set multilocks on*. All of these are scoped to the data session as well. If you have a form with a Private DS, you have to set all these again as well as *set talk* and many other set parameters. See the *SET DATASESSION* topic in VFP help for all the parameters scoped to a DS.
>
>
>Eric (via Mark)
>And don't forget that your project may be opening the database. I've found it a good practice to close the project before I run an EXE for testing.