It's interesting how much of the discussion is about how using one system or
another will appear in the eyes of somebody else. I learned about a naming
convention that makes sense, so I started using it, and found it to be
helpful. It had nothing to do with being a "wannabe". Did you choose the
naming convention you use because you "wannabe" like somebody else? If not,
why do you assume that somebody using another naming convention is driven by
such a motivation?

"Jamie Collins" wrote in message
ups.com...

Robert Morley wrote:
I've seen countless numbers of experienced, formally trained (and who
learned it on their own) database programmers on every platform I've ever
used who use "tbl" for tables, "vw" for views, "usp" for user stored
procedures, not to mention "frm" for forms, "rpt" for reports, etc., ad
nauseum.

I think the important word here is 'convention'.

It is an Access convention to prefix tables with 'tbl'. Wannabe Access
MVPs see established Access MVPs using the prefix so they imitate them;
in turn Access MVPs use the prefix because it's what their audience
expects i.e. to do Access things in an Access way.

Bottom line: use the 'tlb' prefix if you want to appear to be a true
blue Access user. How that affects your reputation as an amateur or
otherwise will largely be determined by where you are posting your
reply e.g. contrast the Microsoft.Public.Access.GettingStarted group
with comp.databases.theory.

My advice: if you want to appear as a 'serious' SQL database type
person, take a look at what people do outside of the Access ghetto.
You'll find the debate focuses on whether to pluralize table names
(e.g. Customer or Customers) and that prefixes are not rarely used at
all, other than as a hangover from a port from Access.

Jamie.

--