Search results

Dear Roy I've read the threads you kindly provided. I don't find anything there that explains the business advantage of using meaningful keys. People are saying "use meaningless" and "use meaningful" but nobody is actually logically justifiying their standpoint. I would really like to add...

Dear Moniker Thanks for taking the trouble to make these points. With your example of Provider, Market and Measure tables with PK's ProviderID, MarketID and MeasureID. Using the meaningful method (as in your system) the MarketID and MeasureID are autonumbers and the ProviderID is a...

There often isn't a "right" and "wrong" answer to many issues. My aim would be to state the pro's and con's of each approach in a very clear and understandable way that everybody (even non-technical people) can instantly understand. I'm very clear on the advantages of meaningless primary keys...

Hi Roy 3-1: "Primary Keys are always meaningless and have the data type: Autonumber" I suppose I thought it was obvious that many-to-many link tables consisting of concatenated foreign keys were an exception... but nothing should be assumed. I've decided to break 3-1 into two in order to...

This standard is published on the web http://metadata-standards.org/11179/#11179-5. The standard makes interesting reading but doesn't (and isn't intended to) provide the type of specific rules for table and field naming included in my standard. More importantly, the paper is written at a very...

Dear Peter Here's my re-draft:- 1-11 Do not use the addition operator to concatenate strings except when propagating nulls. Use & for concatenating strings and + only for arithmetic operations. There are not many cases will you will get a different result if you use the addition operator...

Hi Roy Thanks for your comments. > to download something with huge copyright statements across each page, and "full book available from..." in the header section. I've actually taken this on board. I really didn't think that the watermark would offend anybody but I can see now that I was...

Peter, My first thoughts were that the following is more readable? strIn = "in(" If Not IsNull(Me.myfield1) Then strIn = strIn & Me.myfield1 & ", " If Not IsNull(Me.myfield2) Then strIn = strIn & Me.myfield2 & ", " strIn = strIn & ")" But then I slept on it and began to question the need for...

Dear Peter Thanks a million for the feedback. This is just what I need to kick my thought processes into new directions! > Quote: > 1-12 Do not use the addition operator for concatenating strings. > Use & for concatenating strings and + only for arithmetic operations. > I would argue with...

Hi Mark Thanks for the feedback. The reason I prohibit m_strFirstName in my code is so that when I see an underscore I absolutely know that I'm dealing with a constant (but the all caps is, admittedly, a dead giveaway too). The other reason is that it is just plain old fashioned for me. It...

Thanks for the input on American English/UK English. I would appreciate some feeback on the standards as well! You may be interested to know that all materials on my site are written in American English. I've even included a statement to that effect in: Introduction To The Free Course - 1. I...

Greetings I've published a new programming standard for Microsoft Access VBA on my site http://www.learnaccessvba.com. Most of the "generally accepted" standards are included but I've also included standards for such things as field names, many-to-many link table names, foreign key names...

Error handling tutorial Hi Russ I've put a free tutorial on my site that will tell you everything you need to know about error handling. You do need to include it in every routine but it is very easy with a generic handler you can cut-and-paste. Such a handler is described here :-...