i gues my thinking here is that this function is part of an error trap, therefor it is posible that a form did not completely destroy and the scenario i metioned could occur. since i want the error trap to capture everything i need to trace tables in 'all' datasessions.

if you come up with anything in your research i would appreaciate your findings. i will continue to find a solution, because i am convinced there is one. i'll let you know if i find anything.


>Thanks for the feedback. However, the error handler I referenced is part of an application and is only in effect when the app is running which sounds like a different environment than what you are working with. At any rate I am not sure how my application would encounter the situation you described. When I have some time I will investigate how the condition might occur with something other that the class browser.