Jim Smith wrote:
Wasn't my question.
well ... it was mine but I'll share it with you ;)
Why do you need to label a table as a table?
That was my thought, too.
There is some merit in using
type prefixes in VB because of its loose typing, but it makes no sense in a
database context where the
Andreas,
I don't know of a standard for naming such things. My advice is to group
your table names with a prefix if they are related to one another. Name
fields in such a way that the field's *purpose* is clear to you;
e.g.-checked_out_by, checked_out_date, is_checked_out, etc. Make
Hello list,
is there a common naming system for db objects ?
Thousands.
Like:
1) Tables: mytable, tblmytable, tbl_mytable
2) Indices: idx_anindex
3) Columns: int_somenumber, date_lastupdate
4) id for the numerical primary key e.g. table customers.id
and then for referencing
, August 1, 2003 10:03 am
Subject: RE: standardized naming system ?
Hello list,
is there a common naming system for db objects ?
Thousands.
Like:
1) Tables: mytable, tblmytable, tbl_mytable
2) Indices: idx_anindex
3) Columns: int_somenumber, date_lastupdate
4) id
[mailto:[EMAIL PROTECTED]
Sent: 01 August 2003 15:24
To: [EMAIL PROTECTED]
Cc: [EMAIL PROTECTED]
Subject: Re: RE: standardized naming system ?
Jim,
Great question!
I use the ol'Reddick VBA naming conventions.
tbl - table
idx - index
fld - field
You can search them in google, but I'd like
, 2003 10:39 am
Subject: RE: RE: standardized naming system ?
Wasn't my question.
Why do you need to label a table as a table? There is some merit
in using
type prefixes in VB because of its loose typing, but it makes no
sense in a
database context where the types of objects are quite
