[AccessD] VBA Field Names - Curiosity Question

ROTFL.

That would be RPN if I am not mistaken.

And no I am not Polish either.

I actually learned RPN using an HP calculator back in the late 80s.  Ohhhh what a PITA that was.

John W. Colby

Reality is what refuses to go away
when you do not believe in it

On 7/1/2013 11:59 AM, Steve Goodhall wrote:
> You don't have to be Hungarian, just backwards (as distinct from "backward.")
>
> Steve Goodhall
>
> -----Original message-----
> From: John W Colby <jwcolby at gmail.com>
> To: Access Developers discussion and problem solving <accessd at databaseadvisors.com>
> Sent: Mon, Jul 1, 2013 15:53:58 GMT+00:00
> Subject: Re: [AccessD] VBA Field Names - Curiosity Question
>
> But wait, I am not hungarian!
>
> John W. Colby
>
> Reality is what refuses to go away
> when you do not believe in it
>
> On 7/1/2013 11:44 AM, Tina Norris Fields wrote:
>> Hello Brad,
>>
>> I use Colby's naming convention and I NEVER prefix my field names with a 
> data-type designation.
>>
>> Best,
>> TNF
>>
>> Tina Norris Fields
>> tinanfields-at-torchlake-dot-com
>> 231-322-2787
>>
>> On 7/1/2013 11:01 AM, Brad Marks wrote:
>>> All,
>>>
>>> In a prior life, I was sentenced to work with COBOL for over 30 years.
>>> For the past three years, I spend my time in the world of VBA.
>>>
>>> Since starting to work with VBA, I have been curious about something,
>>> but have never asked about it.
>>>
>>> In the COBOL realm (at least where I worked), we did not indicate the
>>> field type in the field name.
>>>
>>> Examples -
>>> 01 Part-Number   PICTURE X(30).
>>> 01 Part-Cost    Comp-3    PICTURE 9(05).
>>>
>>>
>>> In VBA examples, I see most people using prefixes such as Str, Lng, Dat,
>>> Etc.
>>>
>>> I have never quite understood why people do this when working with VBA
>>> while I believe that very few people did this in the COBOL realm.
>>>
>>> In COBOL we would simply look at the Picture clause in the field name
>>> definition.  This would be the equivalent of looking at the DIM
>>> statement.
>>>
>>> Again, this is just a curiosity question.
>>>
>>> Thanks,
>>> Brad
>>>
>>
>