Re: UI Question: Protecting Critical Delete?

(PeteCresswell) wrote:
Per Rick Brandt:
This is why I dislike prefixing tables with "tbl". If I were doing
what you are talking about I wouldn't have to find and replace all
affected table names. I would simply rename the table and create a
query with the same name that the table formerly had and I'm done.
You don't say that you yourself use the "tbl" prefix, but the
reference to find and replace implies that.

Right. I *always* prefix my table names. "tbl..." "tlkp..."
"zmtbl..." "zstbl".

I would explicitly not want a situation where renaming a query to a
table name would work. Tables are tables. Queries are queries in
my book and I find real value in glancing at a name in the code and
knowing the diff. Kind of like scoping prefixes on variables.

I don't prefix variables either. To me, such naming conventions are no
different than when novices to database design build "smart keys" where multiple
pieces of information are combined into a single field. Objects already have
meta data that is easily available. I see no point in trying to embed that same
data into the name of the object.

Having said that, I make no value judgment about developers who use these
conventions. I just personally don't see the advantage that they claim is there
and see many advantages to NOT using them. It was no surprise to me that the
use of such is now being discouraged in the dot-net world. Microsoft was
largely alone in their common usage to begin with.

--
Rick Brandt, Microsoft Access MVP
Email (as appropriate) to...
RBrandt at Hunter dot com




.

Relevant Pages

  • Re: abstract naming conventions
    ... > We are having a debate in our organization about naming conventions for ... The three proposed methods are: ... > 1) Prefix the class name with abstract. ... Look at the problems that the debate is ...
    (comp.lang.java)
  • Re: abstract naming conventions
    ... > We are having a debate in our organization about naming conventions for ... > abstract classes. ... The three proposed methods are: ... > 1) Prefix the class name with abstract. ...
    (comp.lang.java)
  • abstract naming conventions
    ... We are having a debate in our organization about naming conventions for ... abstract classes. ... The three proposed methods are: ... Prefix the class name with abstract. ...
    (comp.lang.java)
  • Re: splitting a field
    ... Steve Schapel, Microsoft Access MVP ... tgl wrote: ... > some fields have a prefix and/or middlename some do not. ...
    (microsoft.public.access.queries)
  • Re: Object oriented best practices // Creating Objects and ObjectColletions from DataLayer
    ... Another question I had was naming conventions in SQL 2000. ... Currently I prefix my columns like ... I seen Microsoft do UserID as UserID ... use Pascal casing in most cases and camel casing in parameters. ...
    (microsoft.public.dotnet.framework)