>>Are you trying to capture all the open tables and then exit the app? If you are, just have your error routine set a flag, and once you exit the error handler, check the flag and then save your info before exitting the app.
>
>
>no the app will keep running. it is a 'self maintenance' errortrap which desides what to do depending on the error and on the situation the app was in when the error acured. what i am using this for is, when a customer calls they can e-mail me the errorlog and i can see exactly what state the app was in.

This must be why they added the ASESSION() function in VFP7. I don't see how you can get there from here using VFP6 or earlier. Well, since the error occurs in one datasession, what's in the other sessions has only a small potential for impact on what happened. You'll either have to live with what's in your current datasession or upgrade to a more current version of VFP.

One more thought:
You could have a special method on each form that returns it's open tables etc., and you could call that for each form from your error handler, using the _SCREEN.Forms collection to spin through all forms. That's about all that I could think of.