ative VFP tables vs Remote views

We have a LAN with W2k server and W2k workstations. My VFP database is
located in the W2k server. My concern is to access data as fast as possible.
I created a local view to retrieve and update records in 2 tables. When I run
the local view, in the data-session window I can see 3 tables open,
view(cursor) and the 2 tables.
Then I created a remote view using a connection string in which I used
Microsoft Visual Foxpro ODBC Driver. Interestingly, When I run the remote
view, in the data-session only the view(cursor) is open.
Therefore, is it a good idea to use remote views in this way in my forms as
the overhead of opening the native tables on the user's workstation is
eliminated?
Your comment is greatly appreciated.

Gerben
Mon Aug 09 01:13:16 CDT 2004

Hi Don,

Openning Native data must be faster than opening them with a remote view.
(No overhead of ODBC etc etc)
IMO, that Fox does not leave the "remote" tables open, has nothing to do
with speed.

Gerben Kessen.


"Don" <Don@discussions.microsoft.com> wrote in message
news:1BBDD1E1-F665-488D-ABEC-13676BCD2256@microsoft.com...
> We have a LAN with W2k server and W2k workstations. My VFP database is
> located in the W2k server. My concern is to access data as fast as
possible.
> I created a local view to retrieve and update records in 2 tables. When I
run
> the local view, in the data-session window I can see 3 tables open,
> view(cursor) and the 2 tables.
> Then I created a remote view using a connection string in which I used
> Microsoft Visual Foxpro ODBC Driver. Interestingly, When I run the remote
> view, in the data-session only the view(cursor) is open.
> Therefore, is it a good idea to use remote views in this way in my forms
as
> the overhead of opening the native tables on the user's workstation is
> eliminated?
> Your comment is greatly appreciated.
>

Stefan
Mon Aug 09 01:06:53 CDT 2004

When you are working with Fox tables / databases in a LAN or
locally, Remote Views are slower than Local Views because of
the additional ODBC bottleneck.

Local views actually do open their basetables automatically,
but there are no performance issues to worry about related
to that fact.
You can see the effect by creating a test table, say 1.5 GB,
and store it in a shared LAN folder. Then (open a new IDE
instance to avoid data caching and) try
USE \\yourserver\sharedfolder\reallybig.dbf
You'll probably see that it opens very quickly, because Vfp
just asks the operating system to create a file header handle
at that point. The actual data will be fetched and cached on
demand later.


hth
-Stefan

"Don" <Don@discussions.microsoft.com> schrieb im Newsbeitrag
news:1BBDD1E1-F665-488D-ABEC-13676BCD2256@microsoft.com...
> We have a LAN with W2k server and W2k workstations. My VFP database is
> located in the W2k server. My concern is to access data as fast as possible.
> I created a local view to retrieve and update records in 2 tables. When I run
> the local view, in the data-session window I can see 3 tables open,
> view(cursor) and the 2 tables.
> Then I created a remote view using a connection string in which I used
> Microsoft Visual Foxpro ODBC Driver. Interestingly, When I run the remote
> view, in the data-session only the view(cursor) is open.
> Therefore, is it a good idea to use remote views in this way in my forms as
> the overhead of opening the native tables on the user's workstation is
> eliminated?
> Your comment is greatly appreciated.
>

Don
Mon Aug 09 06:23:01 CDT 2004

Hi Guys,

Thank u very much for your clarrifications.

Don

"Stefan Wuebbe" wrote:

> When you are working with Fox tables / databases in a LAN or
> locally, Remote Views are slower than Local Views because of
> the additional ODBC bottleneck.
>
> Local views actually do open their basetables automatically,
> but there are no performance issues to worry about related
> to that fact.
> You can see the effect by creating a test table, say 1.5 GB,
> and store it in a shared LAN folder. Then (open a new IDE
> instance to avoid data caching and) try
> USE \\yourserver\sharedfolder\reallybig.dbf
> You'll probably see that it opens very quickly, because Vfp
> just asks the operating system to create a file header handle
> at that point. The actual data will be fetched and cached on
> demand later.
>
>
> hth
> -Stefan
>
> "Don" <Don@discussions.microsoft.com> schrieb im Newsbeitrag
> news:1BBDD1E1-F665-488D-ABEC-13676BCD2256@microsoft.com...
> > We have a LAN with W2k server and W2k workstations. My VFP database is
> > located in the W2k server. My concern is to access data as fast as possible.
> > I created a local view to retrieve and update records in 2 tables. When I run
> > the local view, in the data-session window I can see 3 tables open,
> > view(cursor) and the 2 tables.
> > Then I created a remote view using a connection string in which I used
> > Microsoft Visual Foxpro ODBC Driver. Interestingly, When I run the remote
> > view, in the data-session only the view(cursor) is open.
> > Therefore, is it a good idea to use remote views in this way in my forms as
> > the overhead of opening the native tables on the user's workstation is
> > eliminated?
> > Your comment is greatly appreciated.
> >
>
>