Relationship problem ~ How to tell Owner his db is crap.

[David Allison]

Relationship problem ~ How to tell Owner his db is crap.
His db was made in 1999 - 12 tables - none normalised - none with
relationships.(YES REALLY)
He only knows about inputing data - 22,000 records.
How does one solve this type of Relationship ?
--
Dave Allison ~ Scotland

[R. Soul]

"David Allison" <da***********@zzzzzzzzzblueyonder.co.uk> wrote in message
news:TB************@news-binary.blueyonder.co.uk...

Relationship problem ~ How to tell Owner his db is crap.
His db was made in 1999 - 12 tables - none normalised - none with
relationships.(YES REALLY)
He only knows about inputing data - 22,000 records.
How does one solve this type of Relationship ?
--
Dave Allison ~ Scotland

Unless there are any issues involving cascade deletes:

CurrentDb.Owner.Terminate

R. Soul

[Lyle Fairfield]

"David Allison" <da***********@zzzzzzzzzblueyonder.co.uk> wrote in
news:TB************@news-binary.blueyonder.co.uk:

Relationship problem ~ How to tell Owner his db is crap.
His db was made in 1999 - 12 tables - none normalised - none with
relationships.(YES REALLY)
He only knows about inputing data - 22,000 records.
How does one solve this type of Relationship ?

Say, "Lyle Fairfield says your db is CRAP!"

--
Lyle
(for e-mail refer to http://ffdba.com/contacts.htm)

[Tom Wickerath]

Chuck,

You might want to refer back to a thread with subject "Relationships", which started with
a post on 7/7/03. In this thread, you may find some useful advice from Michael Kaplan
regarding relationships.
________________________________________

"Chuck Grimsby" <c.*******@worldnet.att.net.invalid> wrote in message
news:jn********************************@4ax.com...

Use as is. What the heck do you care anyways? Most of my databases
do *NOT* have any relations set up in the Relationships window. I do
all that through code and queries. I've been doing databases so long,
I don't need the "relationships window" to do the relating I need to
do, and I tend to find it more of a hindrance then a help.

Now, mind you *all* of my tables are normalized... Indeed, I've been
accused a few times of over normalization (actually, normalizing
beyond what is the minimum requirement to get the job done), but I
take that piece of "advice" with the same grain of salt that I take
when people complain about my lack of use of the "relationships
window".
--
Freedom Defined Is Freedom Denied. - The Illuminatus

[(Pete Cresswell)]

RE/

He only knows about inputing data - 22,000 records.
How does one solve this type of Relationship ?

The guys at CarTalk would probably have an answer.
--
PeteCresswell

[Mike MacSween]

"David Allison" <da***********@zzzzzzzzzblueyonder.co.uk> wrote in message
news:TB************@news-binary.blueyonder.co.uk...

Relationship problem ~ How to tell Owner his db is crap.
His db was made in 1999 - 12 tables - none normalised - none with
relationships.(YES REALLY)
He only knows about inputing data - 22,000 records.
How does one solve this type of Relationship ?

First of all avoid the word crap. Is the owner a database developer? If not
then there's no earthly reason why he should know what normalised tables
are, or what relationships between tables are. And as has been pointed out,
many developers don't use permanent relationships between tables anyway. Of
course he may have expertise in an area where you don't. Like running the
business.

If you're employed there as a database developer then it IS your job to
point out weaknesses in the design, and to suggest how to go about building
a better one. Why normalised tables are better than unnormalised for
instance. BTW you don't say what form they aren't normalised to. Not even
1NF? Or just not BCNF? But if he's managed to get 22,000 records in then
that implies to me that the thing has filled some sort of purpose for the
past 4 years.

If you're not employed there as a database developer say nothing.

My 2p worth.

Mike

[Michael \(michka\) Kaplan [MS]]

The fundamental issue is whether or not integrity is enforced, and if so
then where it is, in fact, enforced.

The Jet database engine can:

1) enforce integrity
2) better optimize indexes
3) generate more efficient query plans

Homegrown CODE solutions will obviously only be able to do #1, and only if
no mistakes are made in the code. Now attempting to re-implement a built-in
piece of functionality that will not have some of the most important
performance benefits is not the best possible idea.
--
MichKa [MS]
NLS Collation/Locale/Keyboard Development
Globalization Infrastructure and Font Technologies

This posting is provided "AS IS" with
no warranties, and confers no rights.

"Chuck Grimsby" <c.*******@worldnet.att.net.invalid> wrote in message
news:6r********************************@4ax.com...

I've been in many such discussions here at CDMA. I may have been in
that one as well, but I don't remember. It's not worth it to me to go
look it up however. As I mentioned in my post, I've been working too
long on databases to require the use relationships window to make my
databases work, and work right. Indeed, as I also mentioned, I find
the relationships window more of a hindrance then a help.

Your results may vary. Please feel free to do whatever you need to do
to get the job done, using whatever skills and tools required. Please
also allow others the same freedom.
On Sun, 2 Nov 2003 04:25:51 -0800, "Tom Wickerath"
<AO***********************@comcast.net> wrote:

You might want to refer back to a thread with subject "Relationships", which started witha post on 7/7/03. In this thread, you may find some useful advice from Michael Kaplanregarding relationships.

"Chuck Grimsby" <c.*******@worldnet.att.net.invalid> wrote in message
news:jn********************************@4ax.com.. .
Use as is. What the heck do you care anyways? Most of my databases
do *NOT* have any relations set up in the Relationships window. I do
all that through code and queries. I've been doing databases so long,
I don't need the "relationships window" to do the relating I need to
do, and I tend to find it more of a hindrance then a help.
Now, mind you *all* of my tables are normalized... Indeed, I've been
accused a few times of over normalization (actually, normalizing
beyond what is the minimum requirement to get the job done), but I
take that piece of "advice" with the same grain of salt that I take
when people complain about my lack of use of the "relationships
window".

--
Central Inteligence Agency... Now There's A Contradiction In Terms