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. |
|
|
|
Thread Tools | Display Modes |
#1
|
|||
|
|||
Naming Conventions Confusion
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 |
#2
|
|||
|
|||
Naming Conventions Confusion
Dee
There is no "right" answer. You are looking at naming "conventions", so you may end up deciding what approach you want to use. Stick with it after you decide! The prefixes don't do anything for Access... they are intended to make your understanding (and that of those who pick up your database/code later) greater. Regards Jeff Boyce Microsoft Office/Access MVP "dee" wrote in message ... 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 |
#3
|
|||
|
|||
Naming Conventions Confusion
Congrats on using naming conventions! In my view tbl is a sufficient prefix
for a table name. I don't think it's necessary to have table types in the prefix. Tables only have one function, to hold data, so all tables are essentially equal. If you do decidd to use special naming conventions for lookup tables, etc., as long as you're consistent it doesn't matter which one you pick. "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 |
#4
|
|||
|
|||
Naming Conventions Confusion
Thank you both for your input.
I get it now! BTW, what the heck is a Title Table? -- Thanks! Dee "mray29" wrote: Congrats on using naming conventions! In my view tbl is a sufficient prefix for a table name. I don't think it's necessary to have table types in the prefix. Tables only have one function, to hold data, so all tables are essentially equal. If you do decidd to use special naming conventions for lookup tables, etc., as long as you're consistent it doesn't matter which one you pick. "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 |
#5
|
|||
|
|||
Naming Conventions Confusion
|
#6
|
|||
|
|||
Naming Conventions Confusion
I've never heard of one...
Regards Jeff Boyce Microsoft Office/Access MVP "dee" wrote in message ... Thank you both for your input. I get it now! BTW, what the heck is a Title Table? -- Thanks! Dee "mray29" wrote: Congrats on using naming conventions! In my view tbl is a sufficient prefix for a table name. I don't think it's necessary to have table types in the prefix. Tables only have one function, to hold data, so all tables are essentially equal. If you do decidd to use special naming conventions for lookup tables, etc., as long as you're consistent it doesn't matter which one you pick. "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 |
#7
|
|||
|
|||
Naming Conventions Confusion
"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 |
#8
|
|||
|
|||
Naming Conventions Confusion
On Jul 31, 11:52 pm, mray29 wrote:
Tables only have one function, to hold data, so all tables are essentially equal. I agree. SQL has but one data structu the table. So why does anyone need to give it a prefix? One issue with the Leszynski naming convention (http:// en.wikipedia.org/wiki/Leszynski_naming_convention) is that there are (at least on some level) two types of table: a base table and a virtual table, the latter being a VIEW i.e. a stored Query object comprising a non-parameterized query that returns a resultset; a parameterized one or 'action Query' is a PROCEDURE. With the LNC, base tables get a tbl- whereas both VIEWs and PROCs get qry- i.e. can't tell which qry- objects are logical tables. Sometimes I want to 'hide' a base table and expose it only via VIEWs -- say, it has some columns which should only be exposed to certain user groups rather than PUBLIC -- and a qry- prefix would give the game away. Sometimes a table starts out as 'public' and only later goes 'private' at which point I want to change the name of the base table and create a VIEW using the base table's former name; under LNC you'd have to rename from tbl- to qry- in all the SQL queries and statements in all the applications that use the table (a.k.a. breaking compatibility). I've been told by a regular in these groups that the tbl- and qry- prefixes are merely to tell an Access developer whether to look on the Tables tab or the Queries tab respectively in the Access environment. If that is the case, I'm not sure why so many Access developers think it is worth the bother. I rather suspect it is a desire to emulate their peers i.e. self-perpetuating; I've even heard someone say, "Call themselves an Access developer? Why, they don't even prefix their tables with tbl-!!" Jamie. -- |
#9
|
|||
|
|||
Naming Conventions Confusion
On Jul 31, 11:52 pm, mray29 wrote:
Congrats on using naming conventions! In my view tbl is a sufficient prefix for a table name. I don't think it's necessary to have table types in the prefix. Tables only have one function, to hold data, so all tables are essentially equal. If you do decidd to use special naming conventions for lookup tables, etc., as long as you're consistent it doesn't matter which one you pick. FWIW see the "Level 2 tags" in the following MSDEN article: Naming Conventions for Microsoft Access http://msdn.microsoft.com/archive/de...n_20naming.asp Jamie. -- |
#10
|
|||
|
|||
Naming Conventions Confusion
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 |
|
Thread Tools | |
Display Modes | |
|
|