Karen - I'm converting an old RB 2.11 and feel your pain, but the vars aren't as bad as yours.  Anything that requires a shift key, even the underscore as in "var_name", should be outlawed (except when used by RBTI :)
And it helps if they'd read column values into similarly named variables:  SEL FirstName INTO vFirstName...
And use the same variable name consistently throughout the project, not vPartNum, vPartNmbr, vPart#

<set shake off>

Doug
p.s.  I just read Bruce's comment (funny) -
Oh wait! 
I know that one. 
That's not a VARIABLE. 
That's an EXPLETIVE.
Maybe your DOS programmer was writing the code with voice recognition software.


[email protected] wrote:
Okay, this is driving me crazy.  Can I vent?   I'm converting an old DOS system.   I've always had a problem with programmers who create variable names that are impossible to follow, but how is this for a good variable name:       v#x4

His programs are loaded with variable names with # and $ and all kinds of characters that must have been a pain to type, and don't mean anything.  The above variable, believe it or not, is for a simple choose menu to trap a customer ID.

<shaking head>

Karen








Reply via email to