Relational Database

[rebecky via AccessMonster.com]

I am distributing an Employer Database I built on Thursday to approximately
20 people. There will be a short training for them on how to use it. I need
to explain to them the reasons why it is so important to have a parent/child
record relationship and I don't know what to say. They want to enter the
same employer over and over and I say the Employer should be the Parent
Record with the Position Requests being the Child Records.

Can anyone state the importance of the relational database so I know how to
explain it to them?

Thank you!!
rebecky

 

[EJ Williams]

I'm no Access MVP but here are a couple:

1) Duplication of effort:Why re-type the same data repeatedly
2) Consistencey: The data should be entered once, correctly. By referencing
the original record the data is not deteriorated in accuracy over time. This
also allows central correction applying to all records. For example, if the
employer address changed it would only need to be updated in the employers
table.
3) Database Size: Although this is no longer much of a concern, why
duplicate this information and grow the database when a single record does
the job.

I hope this helps.

Eric

 

[Beetle]

I am distributing an Employer Database I built on Thursday

Ummmm......

If you built a proper database there would be no need to explain
the RDMS concept to your users because the relationships would be
handled in the background of the application. You forms would control
the user interaction and manage all the data entry.

Since you spent *a whole day* putting together your application, I'm
guessing that all you did was create a few tables and you want the users
to enter data directly in the tables (and you expect them to do this in
the exact manner in which it needs to be done to keep the relationships
intact). This is a disaster waiting to happen. Your data is going to become
completely useless in a very short time (i.e. within hours after
your users begin entering information).

Then again, I could be wrong. Maybe you have the ability to create a
fully functional app (tables, relationships, queries, forms, reports, code,
split, multi-user configured) in one day. If that's the case, I would imagine
that there are a host of companies that would jump at the chance to
hire you.

 

[rebecky via AccessMonster.com]

Dear Beetle: I did not build this database on "Thursday", I am distributing
it on "Thursday". It has actually been a work in progress for months and is
a fully functional app (tables, relationships, queries, forms, reports, code,
split, multi-user configured) and MUCH MORE!!!


I just wanted some tips on explaining why data integrity is important...I
wasn't quite sure how to

I am distributing an Employer Database I built on Thursday

Ummmm......

If you built a proper database there would be no need to explain
the RDMS concept to your users because the relationships would be
handled in the background of the application. You forms would control
the user interaction and manage all the data entry.

Since you spent *a whole day* putting together your application, I'm
guessing that all you did was create a few tables and you want the users
to enter data directly in the tables (and you expect them to do this in
the exact manner in which it needs to be done to keep the relationships
intact). This is a disaster waiting to happen. Your data is going to become
completely useless in a very short time (i.e. within hours after
your users begin entering information).

Then again, I could be wrong. Maybe you have the ability to create a
fully functional app (tables, relationships, queries, forms, reports, code,
split, multi-user configured) in one day. If that's the case, I would imagine
that there are a host of companies that would jump at the chance to
hire you.

I am distributing an Employer Database I built on Thursday to approximately
20 people. There will be a short training for them on how to use it. I need

[quoted text clipped - 8 lines]

Thank you!!
rebecky

 

[rebecky via AccessMonster.com]

Thank you. I will use those reasons and any more that come through in my
explanations

I'm no Access MVP but here are a couple:

1) Duplication of effort:Why re-type the same data repeatedly
2) Consistencey: The data should be entered once, correctly. By referencing
the original record the data is not deteriorated in accuracy over time. This
also allows central correction applying to all records. For example, if the
employer address changed it would only need to be updated in the employers
table.
3) Database Size: Although this is no longer much of a concern, why
duplicate this information and grow the database when a single record does
the job.

I hope this helps.

Eric

I am distributing an Employer Database I built on Thursday to approximately
20 people. There will be a short training for them on how to use it. I need

[quoted text clipped - 8 lines]

Thank you!!
rebecky

 

[John W. Vinson]

Can anyone state the importance of the relational database so I know how to
explain it to them?

The analogy I like to use here is that relational databases use the
Grandmother's Pantry Principle: "A place - ONE place! - for everything,
everything in its place."

As noted elsethread, data integrity and consistancy are the biggest benefits.
You store the employer's name and contact information once, and once only; if
there's an error in it, you correct it once, and once only, and it's corrected
for everyone. If you have two dozen instances and find an error, then you have
to track down all the instances and fix them individually!

 

[rebecky via AccessMonster.com]

Thank you!

The analogy I like to use here is that relational databases use the
Grandmother's Pantry Principle: "A place - ONE place! - for everything,
everything in its place."

As noted elsethread, data integrity and consistancy are the biggest benefits.
You store the employer's name and contact information once, and once only; if
there's an error in it, you correct it once, and once only, and it's corrected
for everyone. If you have two dozen instances and find an error, then you have
to track down all the instances and fix them individually!

 

[Beetle]

My apologies rebecky, I completely misread your opening statement.
--
_________

Sean Bailey

Dear Beetle: I did not build this database on "Thursday", I am distributing
it on "Thursday". It has actually been a work in progress for months and is
a fully functional app (tables, relationships, queries, forms, reports, code,
split, multi-user configured) and MUCH MORE!!!


I just wanted some tips on explaining why data integrity is important...I
wasn't quite sure how to

I am distributing an Employer Database I built on Thursday

Ummmm......

If you built a proper database there would be no need to explain
the RDMS concept to your users because the relationships would be
handled in the background of the application. You forms would control
the user interaction and manage all the data entry.

Since you spent *a whole day* putting together your application, I'm
guessing that all you did was create a few tables and you want the users
to enter data directly in the tables (and you expect them to do this in
the exact manner in which it needs to be done to keep the relationships
intact). This is a disaster waiting to happen. Your data is going to become
completely useless in a very short time (i.e. within hours after
your users begin entering information).

Then again, I could be wrong. Maybe you have the ability to create a
fully functional app (tables, relationships, queries, forms, reports, code,
split, multi-user configured) in one day. If that's the case, I would imagine
that there are a host of companies that would jump at the chance to
hire you.

I am distributing an Employer Database I built on Thursday to approximately
20 people. There will be a short training for them on how to use it. I need

[quoted text clipped - 8 lines]

Thank you!!
rebecky

 

[Paul Shapiro]

Another way to express the same idea is that if there is more than one way
to find any particular piece of information, you can eventually expect to
find more than one answer. There would be no way to know which is the
correct answer, or which answer you should use. Database normalization is
essentially eliminating redundancy. Redundancy is evil. It would require
extreme vigilance to keep multiple copies of the same data identical.
Extreme vigilance does not exist in humans, so it's a whole lot easier to
prevent redundancy in the first place.

 

[Mike Painter]

I am distributing an Employer Database I built on Thursday to
approximately 20 people. There will be a short training for them on
how to use it. I need to explain to them the reasons why it is so
important to have a parent/child record relationship and I don't know
what to say. They want to enter the same employer over and over and
I say the Employer should be the Parent Record with the Position
Requests being the Child Records.

Can anyone state the importance of the relational database so I know
how to explain it to them?

Thank you!!
rebecky

If their name gets entered over and over again, somebody is going to make a
mistake and they will not get paid or credited with work they do.
Reports will be wrong and or hard to explain.

Fred Smith is not the same as Fred Smith to a computer and everybody knows
you spell Lori, Lorri, unless it is Lorrie.