It reads plain as day! Variable Version 4th ( v#x4 ) It is the programmers forth attempt to get it to work!
Sorry, had to do that. I try to make mine a little easier (after getting yelled at! ) v (variable) then a capital letter to get attention of what it could be and capital from where or what. Perhaps a number if I am using it several times and small changes between them ie: file locations and then sub directories. vFileClntId1 vFileClntId2 I try hard and sometimes spend more time watching names. I also try to include simple things so I can use clear var if I am only in one form/eep and want to limit my clear statement. I do recall a protocol on var and name usage and often use that also. It was at a conference about three years ago. Heck it could have been yours! Sincerely, Paul Dewey New Horizon Interlock Inc. New Horizon Safety Diagnostics Inc. www.interlockinfo.com Saving Lives - One Breath at A Time T This e-mail message is intended only for the named recipient(s) above and is covered by the Electronic Communications Privacy Act 18 U.S.C. Section 2510-2521. This e-mail is confidential and may contain information that is privileged or exempt from disclosure under applicable law. If you have received this message in error please immediately notify the sender by return e-mail and delete this e-mail message from your computer. From: [email protected] [mailto:[email protected]] On Behalf Of [email protected] Sent: Wednesday, February 18, 2009 4:57 PM To: RBASE-L Mailing List Subject: [RBASE-L] - Annoying program habits 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
