|
| 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
November 16th, 2007, 12:17 PM
posted to microsoft.public.access.tablesdbdesign
|
|||
|
|||
Numbers in table field names
Quick question for a newcommer
I think I heard or read somewhere that I should not use numbers in table field names, is that true? Thanks -- Message posted via AccessMonster.com http://www.accessmonster.com/Uwe/For...esign/200711/1 
|
|
#2
November 16th, 2007, 01:17 PM
posted to microsoft.public.access.tablesdbdesign
|
|||
|
|||
|
Numbers in table field names
I don't recall any Access restriction on using digits in field names...
However, if you are considering using xxxx1, xxxx2, xxxx3, xxxx4, there is a very good chance that you are attempting to commit spreadsheet on Access. "Repeating field names" (with #s) is what you'd have to do in a spreadsheet, but you won't get the best use of Access' relationally-oriented features and functions if you insist on feeding it 'sheet data. Provide a bit more specific description for a bit more specific suggestion... Examples help. -- Regards Jeff Boyce www.InformationFutures.net Microsoft Office/Access MVP http://mvp.support.microsoft.com/ Microsoft IT Academy Program Mentor http://microsoftitacademy.com/ "dcc15 via AccessMonster.com" u38772@uwe wrote in message news:7b4c4e6e71971@uwe... Quick question for a newcommer I think I heard or read somewhere that I should not use numbers in table field names, is that true? Thanks -- Message posted via AccessMonster.com http://www.accessmonster.com/Uwe/For...esign/200711/1
|
|
#3
November 16th, 2007, 01:17 PM
posted to microsoft.public.access.tablesdbdesign
|
|||
|
|||
|
Numbers in table field names
You can use numbers without problem, but it's recommended that you not start
a field name with a number. -- Ken Snell MS ACCESS MVP "dcc15 via AccessMonster.com" u38772@uwe wrote in message news:7b4c4e6e71971@uwe... Quick question for a newcommer I think I heard or read somewhere that I should not use numbers in table field names, is that true? Thanks -- Message posted via AccessMonster.com http://www.accessmonster.com/Uwe/For...esign/200711/1
|
|
#4
November 16th, 2007, 02:48 PM
posted to microsoft.public.access.tablesdbdesign
|
|||
|
|||
|
Numbers in table field names
I tend to go with the most restrictive "rules" on all user defined names -
tables, columns, queries, variables, etc. 1. May contain ONLY a-z, A-Z, 0-9, and the underscore _ 2. Must start with a letter (upper or lower case) 3. Must be limited to 30 characters (I don't violate this rule with table and column names but may with other names). A large number of the apps I create get upsized to SQL Server, DB2, or Oracle and this avoids issues with table and field names - plus personally, I hate having to enclose mal-formed names in square brackets. I rarely use underscores so mostly I just use letters, starting each word or word part with a capital. For example - CustName, BrokerID, SourceCD, Addr1 (for the first line of an address - this isn't a violation of first normal form - it is a convenience for creating mailing address so the user can determine what goes on each line). "dcc15 via AccessMonster.com" u38772@uwe wrote in message news:7b4c4e6e71971@uwe... Quick question for a newcommer I think I heard or read somewhere that I should not use numbers in table field names, is that true? Thanks -- Message posted via AccessMonster.com http://www.accessmonster.com/Uwe/For...esign/200711/1
|
|
#5
November 16th, 2007, 03:04 PM
posted to microsoft.public.access.tablesdbdesign
|
|||
|
|||
|
Numbers in table field names
I like your rules, Pat. I use very similar rules with some minor exceptions.
All field names are upper case and must include at least one underscore. I use numbers only when necessary, for example your addr1 example. (I would use ADDR_1). Seems silly, I know, but the reason is that it is obvious the name is a table field. -- Dave Hargis, Microsoft Access MVP "Pat Hartman" wrote: I tend to go with the most restrictive "rules" on all user defined names - tables, columns, queries, variables, etc. 1. May contain ONLY a-z, A-Z, 0-9, and the underscore _ 2. Must start with a letter (upper or lower case) 3. Must be limited to 30 characters (I don't violate this rule with table and column names but may with other names). A large number of the apps I create get upsized to SQL Server, DB2, or Oracle and this avoids issues with table and field names - plus personally, I hate having to enclose mal-formed names in square brackets. I rarely use underscores so mostly I just use letters, starting each word or word part with a capital. For example - CustName, BrokerID, SourceCD, Addr1 (for the first line of an address - this isn't a violation of first normal form - it is a convenience for creating mailing address so the user can determine what goes on each line). "dcc15 via AccessMonster.com" u38772@uwe wrote in message news:7b4c4e6e71971@uwe... Quick question for a newcommer I think I heard or read somewhere that I should not use numbers in table field names, is that true? Thanks -- Message posted via AccessMonster.com http://www.accessmonster.com/Uwe/For...esign/200711/1
|
|
#6
November 16th, 2007, 07:12 PM
posted to microsoft.public.access.tablesdbdesign
|
|||
|
|||
|
Numbers in table field names
Seeing names in all upper case reminds me of my mainframe days
 When you get right down to it, I prefer camel case because it is more natural for touch typing. I can never figure out an efficient way to touch type names with all caps. "Klatuu" wrote in message ... I like your rules, Pat. I use very similar rules with some minor exceptions. All field names are upper case and must include at least one underscore. I use numbers only when necessary, for example your addr1 example. (I would use ADDR_1). Seems silly, I know, but the reason is that it is obvious the name is a table field. -- Dave Hargis, Microsoft Access MVP "Pat Hartman" wrote: I tend to go with the most restrictive "rules" on all user defined names - tables, columns, queries, variables, etc. 1. May contain ONLY a-z, A-Z, 0-9, and the underscore _ 2. Must start with a letter (upper or lower case) 3. Must be limited to 30 characters (I don't violate this rule with table and column names but may with other names). A large number of the apps I create get upsized to SQL Server, DB2, or Oracle and this avoids issues with table and field names - plus personally, I hate having to enclose mal-formed names in square brackets. I rarely use underscores so mostly I just use letters, starting each word or word part with a capital. For example - CustName, BrokerID, SourceCD, Addr1 (for the first line of an address - this isn't a violation of first normal form - it is a convenience for creating mailing address so the user can determine what goes on each line). "dcc15 via AccessMonster.com" u38772@uwe wrote in message news:7b4c4e6e71971@uwe... Quick question for a newcommer I think I heard or read somewhere that I should not use numbers in table field names, is that true? Thanks -- Message posted via AccessMonster.com http://www.accessmonster.com/Uwe/For...esign/200711/1
|
|
#7
November 16th, 2007, 08:03 PM
posted to microsoft.public.access.tablesdbdesign
|
|||
|
|||
|
Numbers in table field names
I thought I was the last remaining mainframe coder
I understand, but it is just a way know what I am looking at. As to typing in all caps, If you look on the left side of your keyboard, just above the shift key and just below the tab key, there is a key labeld Caps Lock. I find it very useful. But I still have not found the Any key -- Dave Hargis, Microsoft Access MVP "Pat Hartman" wrote: Seeing names in all upper case reminds me of my mainframe days When you get right down to it, I prefer camel case because it is more natural for touch typing. I can never figure out an efficient way to touch type names with all caps. "Klatuu" wrote in message ... I like your rules, Pat. I use very similar rules with some minor exceptions. All field names are upper case and must include at least one underscore. I use numbers only when necessary, for example your addr1 example. (I would use ADDR_1). Seems silly, I know, but the reason is that it is obvious the name is a table field. -- Dave Hargis, Microsoft Access MVP "Pat Hartman" wrote: I tend to go with the most restrictive "rules" on all user defined names - tables, columns, queries, variables, etc. 1. May contain ONLY a-z, A-Z, 0-9, and the underscore _ 2. Must start with a letter (upper or lower case) 3. Must be limited to 30 characters (I don't violate this rule with table and column names but may with other names). A large number of the apps I create get upsized to SQL Server, DB2, or Oracle and this avoids issues with table and field names - plus personally, I hate having to enclose mal-formed names in square brackets. I rarely use underscores so mostly I just use letters, starting each word or word part with a capital. For example - CustName, BrokerID, SourceCD, Addr1 (for the first line of an address - this isn't a violation of first normal form - it is a convenience for creating mailing address so the user can determine what goes on each line). "dcc15 via AccessMonster.com" u38772@uwe wrote in message news:7b4c4e6e71971@uwe... Quick question for a newcommer I think I heard or read somewhere that I should not use numbers in table field names, is that true? Thanks -- Message posted via AccessMonster.com http://www.accessmonster.com/Uwe/For...esign/200711/1
|
|
#8
November 16th, 2007, 09:18 PM
posted to microsoft.public.access.tablesdbdesign
|
|||
|
|||
|
Numbers in table field names
Cute
but that key isn't in my touch typing repertoire nor is the underscore. I preferred COBOL (I didn't use the you know what key to type that) because it used the dash which was lower case. In fact, typing in COBOL (there I did it again), you didn't need to use the shift key at all. "Klatuu" wrote in message ... I thought I was the last remaining mainframe coder I understand, but it is just a way know what I am looking at. As to typing in all caps, If you look on the left side of your keyboard, just above the shift key and just below the tab key, there is a key labeld Caps Lock. I find it very useful. But I still have not found the Any key -- Dave Hargis, Microsoft Access MVP "Pat Hartman" wrote: Seeing names in all upper case reminds me of my mainframe days When you get right down to it, I prefer camel case because it is more natural for touch typing. I can never figure out an efficient way to touch type names with all caps. "Klatuu" wrote in message ... I like your rules, Pat. I use very similar rules with some minor exceptions. All field names are upper case and must include at least one underscore. I use numbers only when necessary, for example your addr1 example. (I would use ADDR_1). Seems silly, I know, but the reason is that it is obvious the name is a table field. -- Dave Hargis, Microsoft Access MVP "Pat Hartman" wrote: I tend to go with the most restrictive "rules" on all user defined names - tables, columns, queries, variables, etc. 1. May contain ONLY a-z, A-Z, 0-9, and the underscore _ 2. Must start with a letter (upper or lower case) 3. Must be limited to 30 characters (I don't violate this rule with table and column names but may with other names). A large number of the apps I create get upsized to SQL Server, DB2, or Oracle and this avoids issues with table and field names - plus personally, I hate having to enclose mal-formed names in square brackets. I rarely use underscores so mostly I just use letters, starting each word or word part with a capital. For example - CustName, BrokerID, SourceCD, Addr1 (for the first line of an address - this isn't a violation of first normal form - it is a convenience for creating mailing address so the user can determine what goes on each line). "dcc15 via AccessMonster.com" u38772@uwe wrote in message news:7b4c4e6e71971@uwe... Quick question for a newcommer I think I heard or read somewhere that I should not use numbers in table field names, is that true? Thanks -- Message posted via AccessMonster.com http://www.accessmonster.com/Uwe/For...esign/200711/1
|
|
#9
November 16th, 2007, 09:30 PM
posted to microsoft.public.access.tablesdbdesign
|
|||
|
|||
|
Numbers in table field names
Yes, even on the keypunch machines it was all lower case.
I did not even have a terminal for my first two years. It was a COBOL coding sheet, pencils, a pencil sharpener, a box of erasers and a wisk broom. And the IMB flowchart template (which I still have). Good ole COBOL. The War and Peace of programming languages. Fifteen pages before you get to the first executable statment. -- Dave Hargis, Microsoft Access MVP "Pat Hartman" wrote: Cute but that key isn't in my touch typing repertoire nor is the underscore. I preferred COBOL (I didn't use the you know what key to type that) because it used the dash which was lower case. In fact, typing in COBOL (there I did it again), you didn't need to use the shift key at all. "Klatuu" wrote in message ... I thought I was the last remaining mainframe coder I understand, but it is just a way know what I am looking at. As to typing in all caps, If you look on the left side of your keyboard, just above the shift key and just below the tab key, there is a key labeld Caps Lock. I find it very useful. But I still have not found the Any key -- Dave Hargis, Microsoft Access MVP "Pat Hartman" wrote: Seeing names in all upper case reminds me of my mainframe days When you get right down to it, I prefer camel case because it is more natural for touch typing. I can never figure out an efficient way to touch type names with all caps. "Klatuu" wrote in message ... I like your rules, Pat. I use very similar rules with some minor exceptions. All field names are upper case and must include at least one underscore. I use numbers only when necessary, for example your addr1 example. (I would use ADDR_1). Seems silly, I know, but the reason is that it is obvious the name is a table field. -- Dave Hargis, Microsoft Access MVP "Pat Hartman" wrote: I tend to go with the most restrictive "rules" on all user defined names - tables, columns, queries, variables, etc. 1. May contain ONLY a-z, A-Z, 0-9, and the underscore _ 2. Must start with a letter (upper or lower case) 3. Must be limited to 30 characters (I don't violate this rule with table and column names but may with other names). A large number of the apps I create get upsized to SQL Server, DB2, or Oracle and this avoids issues with table and field names - plus personally, I hate having to enclose mal-formed names in square brackets. I rarely use underscores so mostly I just use letters, starting each word or word part with a capital. For example - CustName, BrokerID, SourceCD, Addr1 (for the first line of an address - this isn't a violation of first normal form - it is a convenience for creating mailing address so the user can determine what goes on each line). "dcc15 via AccessMonster.com" u38772@uwe wrote in message news:7b4c4e6e71971@uwe... Quick question for a newcommer I think I heard or read somewhere that I should not use numbers in table field names, is that true? Thanks -- Message posted via AccessMonster.com http://www.accessmonster.com/Uwe/For...esign/200711/1
|
|
#10
November 18th, 2007, 10:42 PM
posted to microsoft.public.access.tablesdbdesign
|
|||
|
|||
|
Numbers in table field names
Klatuu wrote:
I like your rules, Pat. I use very similar rules with some minor exceptions. All field names are upper case and must include at least one underscore. I would never use all caps as it takes a lot more room on the forms and reports when in design view. Let's take this paragraph as an example. I WOULD NEVER USE ALL CAPS AS IT TAKES A LOT MORE ROOM ON THE FORMS AND REPORTS WHEN IN DESIGN VIEW. LET'S TAKE THIS PARAGRAPH AS AN EXAMPLE. tONy -- Tony Toews, Microsoft Access MVP Please respond only in the newsgroups so that others can read the entire thread of messages. Microsoft Access Links, Hints, Tips & Accounting Systems at http://www.granite.ab.ca/accsmstr.htm Tony's Microsoft Access Blog - http://msmvps.com/blogs/access/
|
|
| Thread Tools | |
| Display Modes | |
|
|
Linear Mode
