>2)
>When opening views, Visual FoxPro locks the DBC because view definitions span many records. As the number of users grow, and as the number of views opened and closed by the application grows, sooner or later you'll be fighting for locks on the DBC. Therefore consider the following schema: Develop using a single DBC (which is convenient) but upon distribution create a companion DBC containing only the view information, and make your view opening code or view classes go to the companion DBC for view definitions. Users can then have local copies of the View DBC, and there is no lock contention. More details on Creating DBC for Views.
>http://fox.wikis.com/wc.dll?Wiki~BigSystemPerformanceAndVisualFoxPro~VFP
>-----

This is what I used to do and wld suggest.