>Hi Dave,
>
>To me it appears the behavior is correct. Table1 is already open, so therefore the SQL Select cannot create a cursor with the same name.

Note that first instance of Table1 had an alias other than Table1.

I think the problem is in the way that SQL select "performs the internal equivalent of USE AGAIN" [Help on SELECT - SQL, section on why UDFs in result columns or WHERE clauses will give unpredictable results].

I suspect that the SQL SELECT in the example tries to make the result a "filtered view", and that when it tries to create it with the specified alias it can't, because the first thing it's done is USE AGAIN with the default alias "behind the scenes".

Does that make sense at all? Just trying to brainstorm here.

Cheers,