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 |
#91
|
|||
|
|||
Best Practice for tables?
"David W. Fenton" wrote:
It seems to me that you make more problems for yourself than you solve. To me, having to use brackets all the time is *much* worse of a maintenance issue than translating the coder-friendly names into human-friendly names. Not at all. If it was a PITA putting in square brackets then I would have noticed. It's not. When I need an object name I go to the database container window, pretend I'm going to rename the object and grab the name. I'm done. What could be simpler? Problem solved for both users and coders, and without needing to maintain a translation table or extra properties -- all you'd need to do is follow your naming conventions and camel case everything at each word break. But not worth it to me. My system works and it's no trouble at all. You're trying to solve a problem that doesn't exist. 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/ |
#92
|
|||
|
|||
Best Practice for tables?
"Tony Toews [MVP]" wrote:
(tblCountry) - holds the Country names (tblDispatchMethod) - the service the item is sent by (tblSupplier) - who the item is mailed by Don't bother with the tbl prefix. Basically it's a waste of time. Another thing I came across that I instinctively do. When adding a query while in the Query Builder I just hit the first letter of the name of the query and zoom I'm there. No need to scroll, scroll, scroll. This works in all kinds of Access wizard type of list boxes. Now what I could also do is resize the query window and drag and drop from the database container window but that's a bit more awkward for me. 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/ |
#93
|
|||
|
|||
Best Practice for tables?
Kamitsukenu wrote:
K Who would've thought one simple question would bring up, so far 83 postings. Congratulations. I decided to consolidate my postings and create a web page. http://www.granite.ab.ca/access/tony...onventions.htm I also blogged it at http://msmvps.com/blogs/access/archi...nventions.aspx. It'll be interesting to see what comments I get there. (Note that I blog almost all changes, unless minor, to my website so that folks can see what's new or changed.) 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/ |
#94
|
|||
|
|||
Best Practice for tables?
"Tony Toews [MVP]" wrote in
: I don't. Let's stick with Microsoft terminology. But that terminology doesn't distinguish this particular type of subquery from all the others, and I think it needs a name, as it's doing something very different from the others, seems to me. -- David W. Fenton http://www.dfenton.com/ usenet at dfenton dot com http://www.dfenton.com/DFA/ |
#95
|
|||
|
|||
Best Practice for tables?
"David W. Fenton" wrote:
"Tony Toews [MVP]" wrote in : I don't. Let's stick with Microsoft terminology. But that terminology doesn't distinguish this particular type of subquery from all the others, and I think it needs a name, as it's doing something very different from the others, seems to me. From what I recall I don't see any difference between your usage of subqueries and the example from the A97 help. 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/ |
#96
|
|||
|
|||
Best Practice for tables?
"Gina Whipp" wrote in message
... You forgot.... For Freak's Sake (polite term) Thanks for jumping in there Gina, been away for a few days :-) |
#97
|
|||
|
|||
Best Practice for tables?
On Aug 25, 12:29 am, "David W. Fenton"
wrote: Now that I've seen it, I like Jamie's terminology of "derived tables". Yes, that's the term I was trying to come up with. FWIW (quite a lot IMO) it's the term used in the ANSI/ISO SQL-92 spec. Jamie. -- |
#98
|
|||
|
|||
Best Practice for tables?
On Aug 25, 2:35 am, "Tony Toews [MVP]" wrote:
To me, having to use brackets all the time is *much* worse of a maintenance issue than translating the coder-friendly names into human-friendly names. Not at all. If it was a PITA putting in square brackets then I would have noticed. It's not. I too find it a PITA to add square brackets (a proprietary feature; Standard SQL uses double quotes). Are you the only person who will *ever* write SQL against your mdb's? I always consider the person who will 'inherit' my code as well as the current and future users. What about when you ask for help in the 'groups g? Jamie. -- |
Thread Tools | |
Display Modes | |
|
|