Access: This is too much data spreadsheet

[Guest]

Patty approaches you about a problem she has managing all of her
spreadsheets. She has placed a bunch of information about her business in a
huge spreadsheet that looks like this:
____________________________________________________________________
[Customer ] [Address ] [City ] [State ] [Zip code ] [Phone ]
[Store ]
[Name ] [ ] [ ] [ ] [ ]
[ ] [ ]
____________________________________________________________________
[Job ] [Description ] [City ] [State ] [Zip code ] [Job
Notes ]
[No. ] [ ] [ ] [ ] [
] [ ]
____________________________________________________________________
[Payroll Date ] [Payroll ] [Check No. ]
[Amount] [Employee ]
[ ] [Classification ] [
] [ ] [ ]
____________________________________________________________________
[SSN ] [Employee ] [Title ] [Rate ]
[Check Date ][ ] [Number ] [
] [ ] [ ]
____________________________________________________________________

She needs a better solution. This is too much data, and it is too
complicated to maintain in a spreadsheet. But first, you must conceptualize
the business problem in a way that makes sense to a database.

What entities do you see here, and what relationship do you see among
entities?

What are the attributes of the entities?

What are the domains of values that could be stored under each attribute?


(e-mail address removed)

 

[Guest]

I though the idea of you being set a question to answer or a problem to solve
was that you answered or solved it yourself and in doing so not only proved
to your assessor that you had completed the task. Also (more importantly)
you actually learnt how to answer or solve it and didn’t simply post the
whole thing on to a forum

 

[ThePandaManCan]

EqualacornLady,

Visit this link for a basic crash course on databases. It will
help you answer your questions:

http://dotatmac.mcmaster.ca/db_basics/db_01_home.htm

-ThePandaMan

I though the idea of you being set a question to answer or a problem to solve
was that you answered or solved it yourself and in doing so not only proved
to your assessor that you had completed the task. Also (more importantly)
you actually learnt how to answer or solve it and didn't simply post the
whole thing on to a forum
--
Wayne
Manchester, England.

Patty approaches you about a problem she has managing all of her
spreadsheets. She has placed a bunch of information about her business in a
huge spreadsheet that looks like this:
____________________________________________________________________
[Customer ] [Address ] [City ] [State ] [Zip code ] [Phone ]
[Store ]
[Name ] [ ] [ ] [ ] [ ]
[ ] [ ]
____________________________________________________________________
[Job ] [Description ] [City ] [State ] [Zip code ] [Job
Notes ]
[No. ] [ ] [ ] [ ] [
] [ ]
____________________________________________________________________
[Payroll Date ] [Payroll ] [Check No. ]
[Amount] [Employee ]
[ ] [Classification ] [
] [ ] [ ]
____________________________________________________________________
[SSN ] [Employee ] [Title ] [Rate ]
[Check Date ][ ] [Number ] [
] [ ] [ ]
____________________________________________________________________

She needs a better solution. This is too much data, and it is too
complicated to maintain in a spreadsheet. But first, you must conceptualize
the business problem in a way that makes sense to a database.

What entities do you see here, and what relationship do you see among
entities?

What are the attributes of the entities?

What are the domains of values that could be stored under each attribute?


(e-mail address removed)

 

[ThePandaManCan]

My bad, posted the wrong link:

http://www.htmlgoodies.com/beyond/reference/article.php/3472691

This one is much more helpful, and not library-specific.

-ThePandaMan

EqualacornLady,

Visit this link for a basic crash course on databases. It will
help you answer your questions:

http://dotatmac.mcmaster.ca/db_basics/db_01_home.htm

-ThePandaMan

I though the idea of you being set a question to answer or a problem to solve
was that you answered or solved it yourself and in doing so not only proved
to your assessor that you had completed the task. Also (more importantly)
you actually learnt how to answer or solve it and didn't simply post the
whole thing on to a forum
--
Wayne
Manchester, England.

Patty approaches you about a problem she has managing all of her
spreadsheets. She has placed a bunch of information about her business in a
huge spreadsheet that looks like this:
____________________________________________________________________
[Customer ] [Address ] [City ] [State ] [Zip code ] [Phone ]
[Store ]
[Name ] [ ] [ ] [ ] [ ]
[ ] [ ]
____________________________________________________________________
[Job ] [Description ] [City ] [State ] [Zip code ] [Job
Notes ]
[No. ] [ ] [ ] [ ] [
] [ ]
____________________________________________________________________
[Payroll Date ] [Payroll ] [Check No. ]
[Amount] [Employee ]
[ ] [Classification ] [
] [ ] [ ]
____________________________________________________________________
[SSN ] [Employee ] [Title ] [Rate ]
[Check Date ][ ] [Number ] [
] [ ] [ ]
____________________________________________________________________

She needs a better solution. This is too much data, and it is too
complicated to maintain in a spreadsheet. But first, you must conceptualize
the business problem in a way that makes sense to a database.

What entities do you see here, and what relationship do you see among
entities?

What are the attributes of the entities?

What are the domains of values that could be stored under each attribute?


(e-mail address removed)

 

[John Vinson]

Patty approaches you about a problem she has managing all of her
spreadsheets.

Looks like a pretty good course you're taking. Study the materials,
answer the questions - and then come here for clarification of
specific problems.

We won't do your homework for you.

John W. Vinson[MVP]