Sergey

I think you were probably right. The likely cause is a

SQL SELECT

statement fired in a timer that polls a login table for the existence of other users. The regular version changes the currently selected work area by default, however

SELECT ... INTO ARRAY

does not, and my cure is to use this syntax. Few (less than 20) records are expected in the result.

It suggest to me that

SELECT ... INTO CURSOR

could usefully have a 'NOSELECTCURSOR' option for this reason. Obviously it is good practice to use an '.. IN WorkArea' clause to avoid ambiguity wherever possible, but not all statements give you this option.

John Burton

> Do you have a timer that could fire at the
> time of error and run code that could change a work area?