>There are few things in the programmers world that are more infuriating than a good idea badly implemented.
>
>This one really makes my blood boil, but I will bite my tongue (once again) and hope that some day these features will be rectified.
>
>Can you confirm that when I open a view or issue a SQL statement, that all the concerned tables as opened as well and that when I close the resulting cursor that these concerned tables remain opened unless I specifically close them myself?
>
>Why? whywhywhywhywhywhy?
>
Pablo,

As has been said elsewhere in this thread, this is not new behavior. Prior to views, the problem didn't really exist. It was (and is) a sound practice to explicitly open a table prior to executing a query against the table. This allows the programmer to make sure that the table in question isn't currently in exclusive use by someone else. Now it's true that if the table in question is on the Fox path or in the current directory, VFP will do this for you when you execute the query, however, this can lead to problems as well in the case of tables with the same name existing on the Fox path.