Mike, 
I agree with reasoning, but I have a slightly different methodology in that all 
table/database variables AREN'T designated with a type prefix but all 
programming variables are. This way there is never any confusion as I reckon 
that the name in a table should only reflect the contents not the data type. If 
you need to make the data type more obvious then include it in the name i.e:

        Start_Date      D
        Is_Live         L
        Customer_Id     C(20)

Addressing any of these field in mainline programming then becomes trivial and 
you can easily do:

Scatter <Table> name oData

dStart_Date = oData.Start_Date

or declare a local/private variable lIs_Live with no fear of messing things up 
with no confusion.

Personally I am not a fan of the "M." prefix and find it unnecessary.

Just a FWIW.

Dave



-----Original Message-----
From: ProFox [mailto:[email protected]] On Behalf Of 
[email protected]
Sent: 01 August 2017 01:17
To: ProFox Email List <[email protected]>
Subject: Re: GETFILE() Returns Empty String in Some Cases

On 2017-07-31 16:04, Ken Dibble wrote:
> GAAAAAHHH!!! That's it!!
> 
> Not a PRIVATE declaration, the variable is declared LOCAL.
> 
> But in application mode there is a field in an open table with the 
> same name as the variable. I applied the "essential m-dot" to the 
> variable, and that fixed it.


That "variable with same name as a field name" has screwed me in the past more 
than once.  That's why I like my "outdated" variable declarations as pcFilename 
because I definitely don't conflict with MyTable.cFilename.  That works for me. 
 Sorry for the purists who see that as horrible.  lol

[excessive quoting removed by server]

_______________________________________________
Post Messages to: [email protected]
Subscription Maintenance: http://mail.leafe.com/mailman/listinfo/profox
OT-free version of this list: http://mail.leafe.com/mailman/listinfo/profoxtech
Searchable Archive: http://leafe.com/archives/search/profox
This message: 
http://leafe.com/archives/byMID/profox/[email protected]
** All postings, unless explicitly stated otherwise, are the opinions of the 
author, and do not constitute legal or medical advice. This statement is added 
to the messages for those lawyers who are too stupid to see the obvious.

Reply via email to