A Microsoft Office (Excel, Word) forum. OfficeFrustration

If this is your first visit, be sure to check out the FAQ by clicking the link above. You may have to register before you can post: click the register link above to proceed. To start viewing messages, select the forum that you want to visit from the selection below.

Go Back   Home » OfficeFrustration forum » Microsoft Access » Database Design
Site Map Home Register Authors List Search Today's Posts Mark Forums Read  

Naming Conventions Confusion



 
 
Thread Tools Display Modes
  #12  
Old August 1st, 2007, 02:08 PM posted to microsoft.public.access.tablesdbdesign
BruceM[_2_]
external usenet poster
 
Posts: 1,763
Default Naming Conventions Confusion

I use prefixes because it helps me to keep things sorted out in my mind when
I am working on a database. Others, as you have seen, dislike their use.
When I started learning about Access I was told that I should prefix fields
(txt for text, int for integer, dat for date etc.). I have dropped that
approach. Instead, I give the table a short but meaningful name (tblCust,
for instance). The primary key field is CustID. A text box bound to CustID
is txtCustID. The main form based on the table is frmCust. If there are
several Customer forms I add a suffix to the form name. And so forth. It
works for me, but I have read articles that are utterly contemptuous of the
approach. I don't care. If I was working with others on a project I would
be sure we all agreed on the naming convention, but on your own you can make
your own choices. You could adopt a standard naming convention, only to
work with others on a project and find that an entirely different convention
is in use. The main thing is that it needs to work for you.

"dee" wrote in message
...
Well, thanks for all of your input. Now I'm TOTALLY confused! :-)

I know for myself that when I have used code or in various situations
where
I wanted to know what the "entity", I had wished I knew by a prefix.

So, maybe I will just use the simple one and leave it at that.

I will need to look at the links suggested and do some more research!

Thanks again!
--
Thanks!

Dee


"Rick Brandt" wrote:

"Michael Gramelspacher" wrote in message
om...
In article ,
says...
I am creating a database and trying to stick to standard naming
conventions,
using prefixes such as tbl frm, etc.

I have come across two definitions of lookup tables - tlkp and tlu -
and am
not sure which to use.

I also see tjx for join table and ttbl for title table, but am unclear
as to
what these do, especially the title table.

Any guidance would be appreciated!

Do yourself a really big favor and drop the prefix altogether from
table
names.


Agreed. I abhor type-prefix naming conventions.

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





  #13  
Old August 1st, 2007, 04:28 PM posted to microsoft.public.access.tablesdbdesign
mray29
external usenet poster
 
Posts: 61
Default Naming Conventions Confusion

I agree that the tblprevix in Sql server table are not particularly useful.
But in Access, where , lacking a naming convention, when writing or
deciphering code, queries can be confused forms, or tables with queries, etc.
Just ask anyone who has had to take over maintenance of an Access database in
which no naming conventions were used. For example, if a data source for a
form is "Employee", you don't know whether that's a table or a query, and you
have to go find out. However, if the data source is "qryEmployee" or
"tblEmployee", you already know.

"dee" wrote:

I am creating a database and trying to stick to standard naming conventions,
using prefixes such as tbl frm, etc.

I have come across two definitions of lookup tables - tlkp and tlu - and am
not sure which to use.

I also see tjx for join table and ttbl for title table, but am unclear as to
what these do, especially the title table.

Any guidance would be appreciated!
--
Thanks!

Dee

  #14  
Old August 1st, 2007, 04:35 PM posted to microsoft.public.access.tablesdbdesign
BruceM[_2_]
external usenet poster
 
Posts: 1,763
Default Naming Conventions Confusion

Whether or not somebody adds a prefix to a table name, there are other
choices to be made for forms, reports, and other objects, as well as for
controls.
Regarding your latest posting, the OP asked about naming conventions, and
did not advocate one particular approach. Therefore, challenging the OP
with "Tell me how ..." seems unnecessary.
I find it easier when reading SQL to identify tables by way of a tbl prefix,
but I'm sure I could adjust to a no-prefix system if necessary. Another
advantage to a naming convention is that by using a prefix I am very
unlikely to use accidentally one of the many reserved words in Access or
Jet. There are ways of checking for such use of reserved words, but there
is something to be said for a naming system that sidesteps the potential
problem.

"Michael Gramelspacher" wrote in message
om...
In article ,
says...
Well, thanks for all of your input. Now I'm TOTALLY confused! :-)

I know for myself that when I have used code or in various situations
where
I wanted to know what the "entity", I had wished I knew by a prefix.

So, maybe I will just use the simple one and leave it at that.

I will need to look at the links suggested and do some more research!

Thanks again!


Look at Northwind. Tell me how those tables would be enhanced by having
tbl
prefixes dangling in front of them. Look here
http://www.databaseanswers.org/data_models/index.htm and choose any model.
Tell me how a single model table would be enhanced by having a tbl prefix
dangling in from of it.



  #15  
Old August 1st, 2007, 07:37 PM posted to microsoft.public.access.tablesdbdesign
Michael Gramelspacher
external usenet poster
 
Posts: 482
Default Naming Conventions Confusion

In article , mray29
@discussions.microsoft.com says...
For example, if a data source for a
form is "Employee", you don't know whether that's a table or a query, and you
have to go find out. However, if the data source is "qryEmployee" or
"tblEmployee", you already know.


Northwind must be bewildering.g
  #16  
Old August 2nd, 2007, 02:14 PM posted to microsoft.public.access.tablesdbdesign
Dee
external usenet poster
 
Posts: 644
Default Naming Conventions Confusion

Not at all g

Have asked for advice, received it, and have made up my mind on naming
conventions... I suppose everyone could challenge me to agree with their
view...

I appreciate your input!
--
Thanks!

Dee


"Michael Gramelspacher" wrote:

In article , mray29
@discussions.microsoft.com says...
For example, if a data source for a
form is "Employee", you don't know whether that's a table or a query, and you
have to go find out. However, if the data source is "qryEmployee" or
"tblEmployee", you already know.


Northwind must be bewildering.g

  #17  
Old August 2nd, 2007, 06:38 PM posted to microsoft.public.access.tablesdbdesign
Maurice
external usenet poster
 
Posts: 1,585
Default Naming Conventions Confusion

Good for you, the main challenge will be to be consistent in using it. Once
you do that you've convinced yourself that you have made the right choice ;-)
--
Maurice Ausum


"dee" wrote:

Not at all g

Have asked for advice, received it, and have made up my mind on naming
conventions... I suppose everyone could challenge me to agree with their
view...

I appreciate your input!
--
Thanks!

Dee


"Michael Gramelspacher" wrote:

In article , mray29
@discussions.microsoft.com says...
For example, if a data source for a
form is "Employee", you don't know whether that's a table or a query, and you
have to go find out. However, if the data source is "qryEmployee" or
"tblEmployee", you already know.


Northwind must be bewildering.g

 




Thread Tools
Display Modes

Posting Rules
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts

vB code is On
Smilies are On
[IMG] code is Off
HTML code is Off
Forum Jump


All times are GMT +1. The time now is 11:36 PM.


Powered by vBulletin® Version 3.6.4
Copyright ©2000 - 2024, Jelsoft Enterprises Ltd.
Copyright ©2004-2024 OfficeFrustration.
The comments are property of their posters.