Level Extreme platform
Subscription
Corporate profile
Products & Services
Support
Legal
Français
How can I read tables content into memory
Message
From
03/04/2001 12:19:29
Dragan Nedeljkovich (Online)
Now officially retired
Zrenjanin, Serbia
 
General information
Forum:
Visual FoxPro
Category:
Other
Miscellaneous
Thread ID:
00490509
Message ID:
00491389
Views:
9
>I'll have to try that. Most of my lookups are in tables small enough that the difference should be invisible, or else in tables LARGE enough that an array is impossible because of the 65,000 element limit.
>
>However Ascan() has to look at all elements - my gut reaction would have been that it was slower than a Seek.

Coming to think of it, a seek() on a small table requires a lookup at an index block (which is somewhere in the memory) than a corresponding look into the table (which is also small and in the memory), and I figure this would still introduce more overhead than ascan() for really small tables, with a dozen records or so.

It would take some benchmarking to decide when is it better to go for arrays, namely at how many records, but since the mileage may very significantly (depending on the number of fields, type of index, size of the index expression etc etc and not only on the number of records), it's probably going to remain like it is now - "if too much lookup is slow, try with arrays".

back to same old

the first online autobiography, unfinished by design
What, me reckless? I'm full of recks!
Balkans, eh? Count them.
Previous
Reply
Map
View

Click here to load this message in the networking platform