Level Extreme platform
Subscription
Corporate profile
Products & Services
Support
Legal
Français
INDEXSEEK Bug?
Message
From
09/05/2002 10:13:07
Mike Yearwood
Toronto, Ontario, Canada
 
 
To
09/05/2002 09:14:31
General information
Forum:
Visual FoxPro
Category:
Coding, syntax & commands
Title:
Miscellaneous
Thread ID:
00654373
Message ID:
00654459
Views:
24
Hey Ray

Does it really become useless? If you're adding a new record to a buffered table, you could use Indexseek to see if a previous record exists. If not, you do a tableupdate.

Are you saying Indexseek doesn't do this? If you add 2 records in the buffer, do you expect to prevent duplicates within the buffer?

>>>
>>>CREATE DATABASE temp
>>>CREATE TABLE anytable (pkey I PRIMARY KEY, cChar C(6))
>>>SELECT anytable
>>>INDEX ON cChar TAG cChar
>>>SET ORDER TO pkey
>>>SET MULTILOCKS ON
>>>CURSORSETPROP('Buffering',5)
>>>
>>>
>>>Unfortunately, got the exact same results :-(
>>
>>The issue seems to be that the new record hasn't been committed. If you add a TableUpdate() before the INDEXSEEK(), you get the expected results.
>>
>>I am a little surprised by this myself, since the whole point of INDEXSEEK() is to be able to search in buffered tables without committing records.
>>
>>Tamar
>
>Yup, that was exactly my point in saying it renders the function useless. Actually, it's not, of course, I use it all the time in other contexts, but it sure DOES make it useless in checking keys on new records.
Previous
Next
Reply
Map
View

Click here to load this message in the networking platform