I think we have all created our own naming conventions. It definitely helps me out in tracing errors.
Mine are: tables - nothing views - put "vw" at the end temporary tables or view I put "tmp" at the beginning then put a "vw" if it is a view. componentids - I use a "c" prefix variables outside a form - I use a "v" prefix variables inside a form eep - I use a "ve" prefix Dan -----Original Message----- From: Bruce Chitiea Sent: Monday, February 20, 2012 2:32 PM To: RBASE-L Mailing List Subject: [RBASE-L] - Object Naming Conventions All: Any feelings one way or the other about 'prefixed' object naming conventions? ... such as: tb_<tablename> tt_<temptablename> vw_<viewname> fm_<formname> rp_<reportname> Over time, is this helpful in building/maintaining code, or just extra typing? Thanks, Bruce Chitiea SafeSectors, Inc. --- RBASE-L =======================3D======================= D= TO POST A MESSAGE TO ALL MEMBERS: Send a plain text email to [email protected] (Don't use any of these words as your Subject: INTRO, SUBSCRIBE, UNSUBSCRIBE, SEARCH, REMOVE, SUSPEND, RESUME, DIGEST, RESEND, HELP) =======================3D======================= D= TO SEE MESSAGE POSTING GUIDELINES: Send a plain text email to [email protected] In the message SUBJECT, put just one word: INTRO =======================3D======================= D= TO UNSUBSCRIBE: Send a plain text email to [email protected] In the message SUBJECT, put just one word: UNSUBSCRIBE =======================3D======================= D= TO SEARCH ARCHIVES: Send a plain text email to [email protected] In the message SUBJECT, put just one word: SEARCH-n (where n is the number of days). In the message body, place any text to search for. =======================3D======================= D=
