Hi Pablo,
When a user opens a view VFP locks the view definition in the DBC for a
short time. If you're opening and closing views a lot then it can slow
things down. The solution for this problem is to have one DBC for the data
that lives on the network and one DBC for the views that lives on the local
machine. Each user locks his own copy of the view and doesn't collide with
other users.
Cindy Winegarden MCSD, Microsoft Visual FoxPro MVP
cindy.winegarden /at/ mvps DO.T org
-----Original Message-----
From: profoxtech-bounces@leafe.com [mailto:profoxtech-bounces /at/ leafe DO.T com] On
Behalf Of Pablo Rivera Sr
Sent: Tuesday, August 31, 2004 6:22 PM
To: profoxtech@leafe.com
Subject: RE: Views DBC
Interesting, I haven't done view databases where a view references a free
table.
In all the small programs I've written, I use two databases, standard.
One database to hold the real data, i.e.: RealData.dbc; and one database to
hold the views of the data, i.e.: ViewOfRealData.
I am not knowledgeable enough to know why it is a good thing. The reason I
do this is because up to that level of design, I follow the codebook 6.2
model.
©2004 Cindy Winegarden |
