>It was a bit ironic, and only to show that those construction is not the solution for every related problem.

I agree. The real resolution was in the SELECT alias statement being placed after the table was opened with the IN 0 clause. For if the current work area has a table/cursor open, the USE ... In 0 will open the desired table in another work area. So the SELECT statement insures that correct work area current.

>Also I like to mention that SELECT('xyc') does not look for a table. It looks for an ALIAS, even if the alias is the name of the table. It is an alias for the work area what is a number. One should not mix up this.
>
>Other limitation:
>

>CREATE TABLE "mu kuh" (i1 i)
>?ALIAS(), JUSTSTEM(DBF())
>DIR
>?SELECT(JUSTSTEM(DBF()))
>USE
>USE "mu kuh"
>USE "mu kuh" IN SELECT("mu kuh") &&ooops
>USE
>DELETE FILE "mu kuh.*"
>

>
>This is all pretty well syntax (while I would not do that).
>But imagine it on a general procedure. There is nothing wrong with mu ku.dbf

IMO, this is an issue with VFP and dealing with long file names. And you are right that aliases can not have spaces in them.