Level Extreme platform
Subscription
Corporate profile
Products & Services
Support
Legal
Français
Converting application to Client Server
Message
From
06/08/2003 03:36:45
James Beerbower
James Beerbower Enterprises
Hochheim Am Main, Germany
 
 
To
16/05/2003 10:18:02
General information
Forum:
Visual FoxPro
Category:
Client/server
Miscellaneous
Thread ID:
00788732
Message ID:
00817189
Views:
27
Sorry for not answering I haven't had time to read universal thread for the last couple months-- deadlines and a four hour daily commute to Cologne.

Rushmore is a technique that allows certain commands to use indexes without being told what index to use. In the normal LOCATE FOR command no index was used. With rushmore FoxPro will attempt to find an index(es) to use. With some commands you must specify the index to use (SEEK e.g.) with others like SELECT SQL, SET FILTER and so on, one cannot specify which index to use.

Look at "Using Rushmore to Speed Data Access" in the help for a much clearer discussion...

The main tricks
a) "set order" won't speed things up. It actually slows them a tad. In rushmore VFP decides the best indexes.

b) the expression must match the index exactly. That means if you have a lastname + firstname as an index and

SET FILTER TO lastname = "BEAULIEU" it will be really slow even though you have an index.

while if you
SET FILTER TO lastname+vorname = "BEAULIEU" it will be super fast unless there are a lot of BEAULIEU in the database.

On the whole if you have an application where you want to use SQL then you should try to avoid compound indexes.

Take a look at SYS(3054) to see whether your indexes are being used for SELECTS. Unfortunately it won't show anything about SET FILTER...

Jamie

>James,
>
>Maybe I should ask for clarification on what Rushmore Optimized really means. I have several indexes on all of my tables, and I always set the order to the type of index that I need to search on. My dependent tables are all ordered by the key that the relationships are established on (Social Security #, employer ID, etc).
>
>In my code, I try to stay away from "SET FILTER TO", but I do use SEEK and SCAN WHILE commands, which should be Rushmore optimized.
>
>If my tables and searches need to be changed, I'll do whatever I need to. In the meantime, I am also checking out the hardware issues. Since I am not a Network expert, I am relying on what other consultants have said...mainly that our network is set up good and the data transfer should not be a problem.
>
>Thanks!
>
>Fred
James Beerbower
James Beerbower Enterprises
Frankfurt, Deutschland
Previous
Reply
Map
View

Click here to load this message in the networking platform