Level Extreme platform
Subscription
Corporate profile
Products & Services
Support
Legal
Français
Index Bug in VFP9, SP1???
Message
From
20/12/2005 09:18:31
 
General information
Forum:
Visual FoxPro
Category:
Coding, syntax & commands
Environment versions
Visual FoxPro:
VFP 9
OS:
Windows XP SP2
Network:
Windows 2000 Server
Database:
Visual FoxPro
Miscellaneous
Thread ID:
01079481
Message ID:
01079509
Views:
16
>>Not quite a bug, but a peculiarity of foxpro:
>>if you set the index to seq_no, it first tries to find an index with the _name_ seq_no. If that does not exist it will evaluate seq_no. It will then try to set the index to the result of that expression, in this case the result seems to be 1, so it sets the index to 1
>>if seq_no evaluates to "k_memo" the index will be set to k_memo (if it exists)
>>So, if you use an index name, you better use order "seq_no", if you want is as an expression use (seq_no)
>
>I still think it's a bug. If I want VFP to evaliate the name I would use a name expression.

It's called: backwards compatibility.
Even in fox 2.x it works this way, if they change it a LOT of code will stop working.
Previous
Reply
Map
View

Click here to load this message in the networking platform