ArgosReporting/ArgosNamingConventions192016-05-23 16:35:14cox182016-05-23 16:34:25cox172016-05-23 16:34:07cox162016-03-25 15:09:40cox152016-03-23 13:07:45cox142016-03-23 13:07:07cox132016-03-23 13:06:06cox122016-03-23 13:05:33cox112016-03-23 13:05:01cox102016-03-23 13:04:44cox92016-03-23 13:04:21cox82016-03-23 13:03:49cox72016-03-23 13:02:48cox62016-03-23 13:02:17cox52016-03-23 13:02:07cox42016-03-23 13:01:46cox32016-03-23 13:01:32cox22016-03-23 13:00:50cox12016-02-15 16:01:57coxArgos Naming ConventionsGeneral RulesGeneral Forumla: [form]_[type]_[purpose] Casing: Camel case (modified) No spaces are allowed in variable names. An underscore is used to separate words when naming. FormsExamples: main, contacts, charts TypesExamples: main_LB_Degrees, main_DD_CurrTerm BT (Button) CB (Check Box) CH (Chart) DD (Drop Down List Box) DT (Date Entry) EB (Edit Box) LB (List Box) MB (Memo Box) MC (Multi-Column List Box) RB (Radio Button) PurposeExamples: sql_main_GetStudentID, main_DD_CurrTerm, main_LB_Donors The "purpose" should provide a what or how this object will be used. Other Types (SQL / Results)Examples: sql_main_ChrtEnrl (an SQL variable to drive an enrollment chart on form Main … etc) Examples: res_main_MC_AllEnrolled, res_contacts_OLAP_DonatePctTarget Some variables are outside of the Form. With these, we prefix them with the External Type first. sql (SQL) res (Results) Note: As we learn more about the Evisions Argos product, these standards and best practices will grow and be revised to suit our environment more closely.