Level Extreme platform
Subscription
Corporate profile
Products & Services
Support
Legal
Français
Foxpro Life
Message
 
To
15/04/2017 14:04:05
Walter Meester
HoogkarspelNetherlands
General information
Forum:
Visual FoxPro
Category:
Contracts, agreements and general business
Title:
Environment versions
Visual FoxPro:
VFP 9 SP2
OS:
Windows 10
Network:
Novell 6.x
Database:
Visual FoxPro
Application:
Desktop
Miscellaneous
Thread ID:
01649781
Message ID:
01650232
Views:
42
...
>My conclusion on the topic is that you'd better find another way of avoiding the fieldname/variable conflict because realy if you need to know all of this in order to create some code, you should realise that No-one is going to be able to adhere to this standard.

Why not? All one would have to do is to start typing m. in front of your variable references. That's all you need to do, and if you'd start doing it today for any new code that you'd write, your future programs would not create/introduce any further ambiguities.
*
Otherwise, what is your convention for naming variables? I missed that, if you posted it before.
*
Previous
Next
Reply
Map
View

Click here to load this message in the networking platform