Level Extreme platform
Subscription
Corporate profile
Products & Services
Support
Legal
Français
BUG: SEEK/LOCATE/SET FILTER should report an error!
Message
From
26/11/2003 17:06:30
 
 
To
26/11/2003 16:50:14
Dragan Nedeljkovich (Online)
Now officially retired
Zrenjanin, Serbia
General information
Forum:
Visual FoxPro
Category:
Other
Miscellaneous
Thread ID:
00853756
Message ID:
00853898
Views:
20
In critical code we have a lot of things like
   if seek(bintoc(m.nMonat) + bintoc(m.nBeleg), [z_Image])
      assert z_Image.MONAT == m.nMonat and z_Image.BELEG == m.nBeleg
      ...
because the test is affordable and so it would be unwise not to do it. However, tests like these can only uncover cases where an index finds wrong things; they cannot detect other modes of failure like positioning on the wrong record or failing to find a key that is actually present.

So, in the absence of SET INTEGRITY ON we revert to the Turandot principle. I.e., if the question is "How's the index doing today?" we answer (FX: tappety-tap, DELE TAG ALL, INDE ON ...) "Fine, just fine!". *g*

Also, for some critical stuff we force Fox to skip indexes by using expressions that break Rushmore, like FOO+0 etc.
Previous
Reply
Map
View

Click here to load this message in the networking platform