|
Patch reliability is unclear. Unless you have an immediate, pressing need to install a specific patch, don't do it. |
About a month ago we had a very long thread about the problems of naming fields in Access — things like “never name a field ‘name’.”
Does anybody know a site where I can go that explains in SIMPLE steps rules or guidelines for naming fields? What I want is a simple how-to for beginners so they will not fall into any traps later on.
Thanks for your prompt response.
Wow, this is not simple. Are there some rules of thumb somewhere for beginners that say something like:
1. Name all Access objects using a code determining the type. Thus a form about cities should be called “frmcity”.
2. Name all Access fields using the form name as a prefix. For example, if there was a field called city in two tables called “customer” and “employee”, then the respective fields should be called “Customercity” and “employeecity”.
3. and so on….
The above two are merely examples, but demonstrate (hopefully) the format I would like to see. I’m not even sure what I said is true. In my above example, I don’t know whether I should actually have named the city field diffently in each table, particularly if they were related. But don’t answer this question. Hopefully there are a very simple set of general rules out there, otherwise there will be a lot of people a bit frustrated on how to name things. Particularly people who know very little about Visual Basic and don’t understand what Dim means (which is how I feel at times).
Donations from Plus members keep this site going. You can identify the people who support AskWoody by the Plus badge on their avatars.
AskWoody Plus members not only get access to all of the contents of this site -- including Susan Bradley's frequently updated Patch Watch listing -- they also receive weekly AskWoody Plus Newsletters (formerly Windows Secrets Newsletter) and AskWoody Plus Alerts, emails when there are important breaking developments.
