>>>>
>>>>Debugging a private datasession form can be a real challenge (see above about the debugger). You really have to watch where you leave the mouse pointer, as it MAY change rather unexpectedly! Do you have the debug window in it's own frame or is it part of VFP's?
>>>
>>>It's in it's own frame....
>>
>>That's the way I use it, too. Are you sure you're not calling some external piece of code before you look at the current datasession? How are you displaying the datasession? If you have any WAIT WINDOWS, they'll also change the datasession back to default.
>
>Well there are two ways at this point that I have been testing the datasession..
>1) when the form is fully instaniated, I have an "ON KEY..F12..suspend"..
> then "set" from the command window to view the current datasession...
>2) then I HAVE used wait windows in the form's code with a "set('datasession') as the text....that could be misleading

I think ON KEY will also reset the data session. You need to set a breakpoint somewhere in the forms code or on some value the form changes so the datasession doesn't get scrogged on you. I have a Debug Menu that has a option for SUSPEND in it. This leaves the datasession alone. If you use MessageBox instead of WAIT WINDOW, it doesn't change the datasession, either, but then you do have to click OK to continue...