Level Extreme platform
Subscription
Corporate profile
Products & Services
Support
Legal
Français
Detect state of memofield and textbox
Message
 
 
To
16/11/2012 04:55:48
General information
Forum:
Visual FoxPro
Category:
Coding, syntax & commands
Miscellaneous
Thread ID:
01557010
Message ID:
01557441
Views:
61
Koen,

Field name or table name m or local variable name m - this is asking for trouble.

File name 'm.txt' is absolutely OK and 0 trouble.


>>Karen,
>>
>>There's nothing wrong having a file with the name m.txt
>>
>>(1) We're not talking about variables, and
>>(2) Even if we were, there wouldn't be any problem either
>>
>>
>>Don't let them confuse you
>>
>>_________________
>>
>
>Gregory,
>-I see I have started a discussion about the use of mDot, many replies and answers from Tore and Rick.
>I was mainly trying to warn Karen. WIth your above remark you are confusing a 'newbie'
>Technicaly speaking you may be correct in a statement: There is nothing wrong with a file name m.txt
>But it is highly recommend not to use this like that. You are asking for troubles by neglecting a well acknowledged system.
>
>There is nothing wrong in using the mDot notification on the contrary there are only pro's
>
>But it is wrong to say that it is wrong not to use mDot notification
>
>
>Karen,
>let it be clear, you CAN use a file m.txt in this case but you are highly recommended NOT to use it. Afterall what is in it to write
>mText.txt = strofile(myfile)
>instead of
>m.txt = strofile(myfile)
>
>a few keystrokes more and you are assured of always perfect working coding. Besides mText.txt reads more clearly than m.txt to me, but that's highly personal.
>
>P.S. Is your problem meanwhile solved?
>Regards,
>
>Koen
If it's not broken, fix it until it is.


My Blog
Previous
Next
Reply
Map
View

Click here to load this message in the networking platform