Hi Michel-

I have begun to do some benchmarking and these are my preliminary (and somewhat confusing!) results.

Form 1: A blank form based on VFP's base class with a "dummy" table in the DE. (No records, one field)
Form 2: Form 1 + a 2 page pageframe, 3 combo's, 1 check box, 8 text boxes, 1 grid
Form 3: Form1 + four tables (dbf's + cdx's + fpt's > 3 meg)
Form 4: Form1 + four parameterized views (corresponding to the four tables), no data on load.
Form 5: Form4 + set parameter and requery views in activate event.
Form 6: Like form 5, but views are remote using and ODBC connection to a FoxPro database.

I measured the time to load and release each form, first on my local drive then over a 28.8 connection. Here are the results in seconds.
Local 28.8
Form1 0.2 2.9 (blank form)
Form2 0.6 2.9 (a bunch of controls)
Form3 0.4 65 (3.3meg worth of tables in data environment)
Form4 0.6 96 (parametrized local views)
Form5 1.5 344 (requery local views)
Form6 0.8 200+ (requery ODBC views)

Suprises:
1. That using local parametrized views with nodataonload=.T. was SLOWER than the tables themselves (I still don't understand this one--anybody have an explanation?)
2. That over the network, the parametrized ODBC views were not much faster than the parametrized local views. My understanding of local views is that when you run them, the base tables get loaded into the data session whereas ODBC just pulls over the data that matches your parameter. (I am going to try establishing the connection before loading the form ...)
3. That the parametrized ODBC views were faster than the parametrized local views when the data was on my hard disk.

-Mark
>What kind of performance can I expect using ODBC for my retrieving data from fox tables rather than directly using these tables.Its for somebody who want to create an object for retrieving data (présently fox) what ever the type of data.
>
>Michel