Level Extreme platform
Subscription
Corporate profile
Products & Services
Support
Legal
Français
Memory required for Rushmore
Message
 
To
26/10/1999 07:48:23
General information
Forum:
Visual FoxPro
Category:
FoxPro 2.x
Miscellaneous
Thread ID:
00281410
Message ID:
00281439
Views:
13
Hi Somon,

>Oh, I forgot to mention that this has been working fine for about 4 years, then suddenly got really slow... that's why I thougt Rushmore might not be in effect

This means that something has changed recently. Can you imagine what this was?

>I don't know how to find the collate setting of the index. Is this a 2.6 thing?

IDXCOLLATE() is a FoxPro function that returns the collate sequence for an index. The COLLATE sequence specifies how characters are compared. For example with "GENERAL" uppercase and lowercase characters are treated equally. Due to several bugs, you should only use "MACHINE" anyhow.

Anyway, to test wether Rushmore is the culprit, or not, you can try a SCAN NOOPTIMIZE loop (just add NOOPTIMIZE to your SCAN loop). This disables Rushmore. If it takes the same amount as before, Rushmore was indeed disabled. If it's significantly slower, there's something else going on.

You haven't by chance SET OPTIMIZE to OFF somewhere in your code or in the Config.FPW?

How fast is LOCATE FOR and CONTINUE?


Christof
--
Christof
Previous
Reply
Map
View

Click here to load this message in the networking platform