+1
Although I generally only apply HN naming convention to variables only and skip the convention on tables and fields. At most on fields, I'll use a prefix to designate the type of table such as "xref_" for cross reference lookup tables, etc.
Paul H. Tarver Tarver Program Consultants, Inc. Email: paul@tpcqpc.com
-----Original Message----- From: ProfoxTech [mailto:profoxtech-bounces@leafe.com] On Behalf Of mbsoftwaresolutions@mbsoftwaresolutions.com Sent: Monday, July 31, 2017 7:16 PM To: profoxtech@leafe.com 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]