>Hi Dragan,
>I don't think it has anything to do with a prg. You've probably noticed that moving the mouse changes the datasession in the Watch window. I think Christof's datasession rules outlined on the Wiki explain the situation. I strongly believe that SET DATASESSION TO something should be avoided and in its place just instantiate inside session objects where you have that need.

That's why I alternately proposed the Use Again solution. I didn't play much with switching datasessions (just once I wrote a method in a form which would copy all the SETs from the default DS and made damn sure it returned to a proper DS in the end), but we're using ProMatrix here, and it heavily relies on such switchings. It works, but you have to be very careful not to disturb it. Specially nasty is the habit of the oApp object to switch to default DS while its method executes, which makes anything table-related you set in Watch window flip between the regular value and "can't evaluate".

As for the "moving the mouse changes the datasession", I haven't observed that. When does that happen?