Level Extreme platform
Subscription
Corporate profile
Products & Services
Support
Legal
Français
Is SEEK faster than GOTO?
Message
From
08/06/2004 01:56:25
Dragan Nedeljkovich (Online)
Now officially retired
Zrenjanin, Serbia
 
General information
Forum:
Visual FoxPro
Category:
Databases,Tables, Views, Indexing and SQL syntax
Miscellaneous
Thread ID:
00910871
Message ID:
00911014
Views:
20
>I have a function that needs to move around a dbf and then return to the record where the call was made. Should I seek my way back or is a GOTO okay?

Just to add one gotcha (not for you, you probably know this, but for the benefit of our newbies) - if you have table buffering on, recno() will be negative for added records. If you tableupdate() meanwhile, these records will get their real record numbers. If you tried to save the recno() and then tried to GOTO such a saved number, and that number was negative, you may be out of luck.

Other than that, yes, of course it's saver. The question is what's more reliable. If you know exactly what you're doing, go. I mean, GoTo.

back to same old

the first online autobiography, unfinished by design
What, me reckless? I'm full of recks!
Balkans, eh? Count them.
Previous
Reply
Map
View

Click here to load this message in the networking platform