>>>I'm stumped by the error in the title on the 2nd line. I catched this in the error log at a clients, so no repro.
>>>Its intermittend.
>>>
>>>

SELECT InvestLimits
>>>SET ORDER TO Itemid

>>>
>>>
>>>There is no variable called Investlimits, just an alias. The first line has no problem, but it bangs on the SET ORDER TO ItemID.
>>>
>>>Anyone have an idea?
>>
>>I've got a suspect now...
>>
>>The two lines above are part of a method on an object that is called from a dynamicBackColor property in a grid which lives in another datasession.
>>I've seen this before where such a construct could lead to a method call being executed in the wrong datasession.
>>
>>I'll make some modifications and see whether this resolves the problem.
>>
>>Thanks everyone, but I do not think it has to do with anything being fired between the two lines of code. Its quire rare but structural.
>>I think its a VFP bug.
>>
>>Walter,
>
>It is not a VFP bug, it is by design.
>To us it has happened the same thing.
>You must find out which code is executed between the two lines,
>and modify it so that it preserves the active workarea.


Fabio, there is not code executed between the lines. I'm convinced of that. The problem is in the grid control that calls this method.
If you have expressions in either the controlsource, or dynamic properties that call to methods in other datasessions you occasionally get to execute code in the wrong datasession.
I've seen that before. I had to workarround that.

Walter,