Hi Peter ---

I use a bastardized form of standard notation, but close to the Codebook standards. For memory variables, I rarely use scope indicators unless the scope is unusual. For example, variables are scoped by default to local so why use a local indicator unless the var is not local? I do use type indicators, though, for example: dToday, cName, nAmount.

Mixed case on vars and PEMS, lower on system files, tables, fields, upper case for keywords and constants or THIS,THISFORM.....

For object properties, I use mixed case and just call 'em as they are. For example, oApp.CurrentUser.

Non-visual objects are always preceded by "o".

Visual objects are always preceded by a three-letter identifier as to type (almost exactly as in Codebook), i.e., txt=Textbox,cbo=Combobox,ebo=EditBox...etc.

I'm a bit wishy-washy on views. If I'm running a single-tier system with nothing but local views, I'll use vue as a prefix more often than not. If multi-tiered with local and remote I'll use lvw for local and rvw for remote; I'll also use con for connections.

Last but not least, I try to name controls with a prefix of type and the name = to the controlsource name. For example, txtLastName for a TextBox control that
maps to personnel.lastname.