We are running a VFP application on a network. We are accessing all the data from the database using local views. Views will be created programmatically during runtime.

Problem1:

If hundred users are accessing and creating views the DBC will be crowded and the performance will go down.

Problem2:

One user will create a view named View1 on Table1 based on Condition1. Another user also creates the same View1 on Table1 based on different condition Condition2. (The WHERE clause of the select statement will change.)

To avoid these problems, we are maintaining a temporary DBC for every user and saving views created by that user in his/her own temporary DBC.

We don't know whether this is the write way to do this?

Any comments or suggestions in this regard will be appreciated.

TIA.