Level Extreme platform
Subscription
Corporate profile
Products & Services
Support
Legal
Français
SET KEY TO problem
Message
From
28/08/2003 19:29:43
Mike Yearwood
Toronto, Ontario, Canada
 
 
General information
Forum:
Visual FoxPro
Category:
Other
Miscellaneous
Thread ID:
00824329
Message ID:
00824415
Views:
25
See the response I just posted. SET KEY and SET FILTER are radically different IMO.

>That essentially is what a SET KEY is.
>
>
>>Only if a filter is in effect.
>>
>>>LOCATE is usually faster than a GO TOP.
>>>
>>>
>>>>Why are you using LOCATE after a SET KEY? GO TOP should be faster.
>>>>
>>>>>HI,
>>>>>
>>>>>I've a large table (100K+ records that takes up about 75MB) that is giving me fits (C000000005 errors) when the follow is done:
>>>>>
>>>>>SELECT lsealt
>>>>>SET ORDER TO TAG lseacctnum
>>>>>SET KEY TO m.lseacctnum && variable assigned a value
>>>>>LOCATE
>>>>>
>>>>>Usually the LOCATE causes the problem. But to make matters more confusing is that I don't get this when I use VFP6. Only when running the code in VFP7.
>>>>>
>>>>>I've recreated indexes, copied the records to a Temp table and renamed it back. Nothing works. I don't want to compile under VFP6.
>>>>>
>>>>>Anyone know about any quirks with SET KEY TO ?
>>>>>
>>>>>Thanks
Previous
Next
Reply
Map
View

Click here to load this message in the networking platform