Level Extreme platform
Subscription
Corporate profile
Products & Services
Support
Legal
Français
Speed issues
Message
From
18/07/2003 15:38:12
Mike Yearwood
Toronto, Ontario, Canada
 
General information
Forum:
Visual FoxPro
Category:
Other
Title:
Miscellaneous
Thread ID:
00811416
Message ID:
00811646
Views:
14
locate can be faster than go top when a filter exists. But generally, GO TOP should be faster.

>Here are some false Speeding issues reported by somebody
>
>Test it yourself and see.
>
>False statements:
>1. locate is much faster than a got top because its rushmore optimized. Got a 20-50 times faster with a got top instead
>2. do while !eof with skip is slower than scan .. endscan got a 6 times faster with do while !eof() .. skip +1 ... enddo
>
>Here is a real speed issue:
>
>1. Locate for !empty(date), or locate for date#ctod("") - use - locate for date#{} instead and get a 3-10 times faster command
>2. use the occurs() command instead of checking each character and get 300 times faster for those who didnt use it in their CSV commands.
>3. Set database to DATABASE and use table instead of use DATABASE!TABLE and get 2.5 times faster
>4. Only in development : Disable your standard symbol bar, because it shows the actual Database which has a great influense on the speed of set database to command
>
>Universalthread wishes:
>1. I would appreciate to have a Form with speed test commands in universalthread possibly with a grid on it showing the differences between the speed of commands.
>2. A similar to the speed test form but now for all the errors to let Microsoft use this form to repair VFP
Previous
Reply
Map
View

Click here to load this message in the networking platform