Date:  01/11/2007 09:32:37 AM Msg ID:  003273
From:  FoxWeb Support Thread:  003266
Subject:  Re: Problem in Select-SQL
I was not aware of query performance differences between tables created in FoxPro 2.6 and VFP, but, unless you are still using FP 2.6 on your local workstations, you can easily work around this problem by converting all your old tables.
FoxWeb Support Team
support@foxweb.com email
Sent by Fernando Medan on 01/10/2007 07:22:55 AM:

I was making a revision and repeating test programs and I verified that the difference is not in 1.x compatibility.

The difference seems to be in the use of two similar tables, of different versions: Fox 2.6 y VFP.

Examples: 

VFP table (Numeric Field)
test.dbf (281.424 records)

Time 1: 11:45:20
SQL Query: select nombre from test where id_test=200029 order by nombre into cursor list1
Time 2: 11:45:20

Records: 1

Fox 2.6 table (Numeric Field)
test_26.dbf (281.424 records)

Time 1: 11:47:29
SQL Query: select nombre from test_26 where id_test=200029 order by nombre into cursor list1
Time 2: 11:47:29

Records: 1
VFP table (Character Field)
test.dbf (281.424 records)

Time 1: 11:49:32
SQL Query: select nombre from test where nombre="PAULA" order by nombre into cursor list2
Time 2: 11:49:32

Records: 24
Fox2.6 table (Character Field)
test.dbf (281.424 records)

Time 1: 11:50:31
SQL Query: select nombre from test_26 where nombre="PAULA" order by nombre into cursor list2
Time 2: 11:50:55

Records: 24

The quest is slower using Fox2.6 2,6 table  with field of characters. Any idea of the reason?

Thank you very much.

Fernando Medan 

Sent by FoxWeb Support on 01/09/2007 10:56:23 PM:
I can't find a reason why this setting would cause any difference in query performance.  Enabling 1.x compatibility adds a few extra steps at the beginning of each request, all related to populating the various properties of the CGI object.  Could it be that this is a coincidence and that the performance improvement had to do with a re-start of FoxWeb, reboot, or other factor?  I would really appreciate it if you re-enabled the setting a ran an additional test.