>Is InvestLimits previously involved as a target in a relation that may be destroyed when setting the new order?

No.

>>>Any timers around that could switch work area?
>>
>>Yes, there are timers, but it happens too often just between those lines and nowhere else (in this million+ codeline app).
>>I'm beginning to suspect it is a problem that its at the wrong datasession. Still does not explain why it passes the 1st line without a problem.
>>
>>
>>
>>
>>
>>>>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?