[AccessD] Ambiguous Name

That's the kind of thing my former employer decided to do when we moved to
VB.Net.  Made it very easy to sort things into groups by name, but it was a
nightmare if you wanted to look at, say, all subreports.  I hated it because
it solved one "problem" by creating others.

Charlotte Foust

On Mon, Sep 19, 2011 at 4:56 PM, Arthur Fuller <fuller.artful at gmail.com>wrote:

> 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
>
>
>