>Hi,
>
>>>
>....or possibly you've changed the datasession (or some control has changed the datasession) from what the form is using. If you don't put it back to where you start from, you can end up with this same situation.
><<
>
>Can you give an example of this behaviour ?
>
>Regards,
>Viv


I've not seen it happen in all circumstances, but I have seen strange things occur when you change the datasession manually and don't put it back where you found it. Usually you end up with the infamous C...5 error, but I have seen forms that wouldn't close and/or datasessions that don't go away. These show up as "unknown" if you use the SET command.

I've used objects that are declared in the main startup program, and need to be access tables from forms with private datasessions. Those objects have to be sure to do their own "housekeeping" particularly when it comes to data sessions.

Fred