I've seen it before in cases where changes to the recordsource table, or its order/relationships are causing a grid to auto-refresh, and DynamicBackColor is definitely very sensitive to that. Possibly, other grid events (like Before/AfterRowColChange) might trigger as well. Needless to say, the code you posted should not belong in a function executed on DynamicBackColor ...

>>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,