Level Extreme platform
Subscription
Corporate profile
Products & Services
Support
Legal
Français
How can SEEK() return .T. but have the wrong record?
Message
General information
Forum:
Visual FoxPro
Category:
Databases,Tables, Views, Indexing and SQL syntax
Miscellaneous
Thread ID:
00903416
Message ID:
00903761
Views:
22
What is the setting of SET NEAR when this happens? It should be OFF. If it is now off. You might set a break point on SET('NEAR') to catch where it gets changed.

>David,
>
>Thanks for your quick reply.
>
>I am not depending on the messagebox to monitor what is going on. I inserted that code defensively in cases when i wasn't running this under the debugger. With the debugger, I am actually displaying the value contained in the SEEK argument in the Watch window.
>
>In answer to your other question: the treeview key value is the value of the LOCID + '_', and I am monitoring that in the watch window, as well as val(THISFORM.NodeX.Key) to confirm that it is returning the correct LocID.
>
>The thing that is odd here is that the SEEK() works correctly the first time, but not the second time. It returns .T., but sets the record pointer to record #1.
>
>Again, note that LocID is an integer, not string. The seek shouldn't be confused by things like spaces or extra decimal places.
>
>I have tried deleting the CDX file, and then recreating it. That didn't fix anything.
>
>Jim
Mark McCasland
Midlothian, TX USA
Previous
Next
Reply
Map
View

Click here to load this message in the networking platform