Re: Separate PK in Jxn Tbl?
Date: Sun, 27 Jan 2008 13:53:52 GMT
Message-ID: <Q10nj.196$Tb6.187_at_trndny07>
"Brian Selzer" <brian_at_selzer-software.com> wrote in message
news:MOUmj.1465$uE.920_at_newssvr22.news.prodigy.net...
> Well, that's just dumb. Checks in code can reduce database round-trips,
and
> therefore can improve performance, but are not and cannot be a substitute
> for constraints on the tables. It is the constraints on the tables that
> keeps garbage out of the database.
The idea of keeping garbage out of the database takes on an entirely
different meaning if you are dealing with hundreds of programs written in
COBOL, Java, or anything in between accessing a single Oracle database on
the one hand. On the other hand, if you are a developer creating a self
contained MS Access database cum application (tables, queries, forms,
reports, modules, etc.) all in one file, the same issues arise, but they
are resolved quite differently.
I'm not saying either one is "right" or "wrong". I'm just suggesting why an
objection that makes perfect sense to you and me might be lost on the MS
Access community.