Hi Zlatko,

A SQL statement all by itself should not cause trouble like you describe. Is there any chance that you have a function within the SQL statement that might be messing things up?
Alternatively, I guess a SQL output table with the same names as one already open could cause difficulty. Finally, maybe it would be worth trying the NOFILTER clause to see if that makes a difference.

Good luck,

Jim N

>In my project there is a sub-program, which is called from different programs, forms or objects. It execute some SQL statements and prepare a new table as a final result. It works fine, but there is a problem with diferent environments from where my sub-program was called. Sometimes all tables are closed, sometimes there is two or three tables or even cursors opened and it is important that when sub-program finished its work, everything is just as it was before the sub-program starts, even the record positions in all data areas.
>So, I think, the sub-program must first find out what tables and cursors are opened, what is the order on that tables, what is the relations between them and record positions on each. With execution of an SQL statement tables are opened automatically, so it's rather complicated to finish the job correctly.
>Is there any simple solution for my problem?
>
>Thanks, Zlatko.