Level Extreme platform
Subscription
Corporate profile
Products & Services
Support
Legal
Français
Speeding up a lookup with a large character field
Message
From
12/02/2002 01:31:18
 
 
To
11/02/2002 18:57:17
General information
Forum:
Visual FoxPro
Category:
Databases,Tables, Views, Indexing and SQL syntax
Miscellaneous
Thread ID:
00618638
Message ID:
00618688
Views:
12
Hi Rick,
I've found that INDEXSEEK is slower than SEEK if SET DELETED is ON because it has to move the record pointer to check if the record is deleted and them move it back. So it will depend on her setup.


>Michelle,
>
>... provided you are on the source table to search...
>
>lfound=INDEXSEEK(whatIwant, .T.)
>
>IF lfound
> .... get the file stuff you want... the record pointer has moved there...
>ENDIF
>
>See HELP for INDEXSEEK()
>
>HTH
>
>Ric
>
>>I have a cursor that contains every directory on my hard drive. Given a path, I need to find the record. Even taking a chance by limiting the field to 240 characters so I can SEEK instead of LOCATE, it's still unacceptably slow.
>>
>>I'm wondering if it's possible to make it faster. I thought about making a smaller key field that takes the full path and condenses it into something smaller. There are a couple problems with that, though. First, I don't have any idea how to change the path into something smaller that will still be unique. Second, whatever function does the conversion, plus the SEEK after needs to be faster than just SEEKing on the path.
>>
>>Anyone have any suggestions?
>>
>>Thanks,
>>
>>Michelle
Previous
Next
Reply
Map
View

Click here to load this message in the networking platform