[AccessD] Ambiguous Name

Heenan, Lambert Lambert.Heenan at chartisinsurance.com
Tue Sep 20 10:49:16 CDT 2011


I'm 100% with you on this Arthur. Been using a variation on the theme for years. I especially like being able to 'find' objects in the database window by typing the initial few letters of the name. 

Suffixes for me, not prefixes.

Lambert  


-----Original Message-----
From: accessd-bounces at databaseadvisors.com [mailto:accessd-bounces at databaseadvisors.com] On Behalf Of Arthur Fuller
Sent: Monday, September 19, 2011 7:57 PM
To: Access Developers discussion and problem solving
Subject: Re: [AccessD] Ambiguous Name

First of all, I am semi-retired, after 25+ years in the trenches.
Second, I am an opponent of Hungarien (Simonyi) notation. I invented my own school of notation, which I call (in homage to the aforementioned) Post-Hungarian. In a nutshell this means:

frm_MyForm --> MyForm_frm. And so on for all objects in said project. Why adopt this convention? Because all the objects related to, let's say, Customer, are all sorted naturally, I can find everything related to Customer easy as pie. At the end of the day, I am most interested in retrieving said objects. I go further. I have suffixes including "_qs", "qu", "qd" and "qi" and these mean "query select", "query update", "query delete" and "query insert"/ The point being that the prefix "Customer..."
sorts the people according to what they affect, and from there I can work out what is destined to do something to the underlying data.

Granted, this is only my opinion on how objects ought to be named. Smarter people on this list might come up with superior schemes,

A.
--
AccessD mailing list
AccessD at databaseadvisors.com
http://databaseadvisors.com/mailman/listinfo/accessd
Website: http://www.databaseadvisors.com




More information about the AccessD mailing list