>Consider a parameterized view named CLIENT_VIEW. I'm going to open two instances because I need to.
>
>USE CLIENT_VIEW Alias Clients1
>* Now assume you want a different data set, so assume
>* the view parameter has been changed (code not
>* shown)
>Select 0
>USE CLIENT_VIEW Alias Clients2
>
>Now, even though you can SELECT CLIENTS1 and SELECT CLIENTS2 and work with both views just like they are tables, the first instance (alias CLIENTS1) is no longer accessible to a select-SQL statement. This seems kind of screwy. For example, both of these views are in fact cursors that exist as temporary files. Neither of them exist as a table called CLIENT_VIEW. Yet Foxpro's SQL can only find the most recent instance of CLIENT_VIEW. You have to reference views by the name of the view, not the alias name, so you cannot access both views in the same SQL statement.
>
>Is there a workaround for this?


Private data sessions?

Tom