Allen-
Try Database Design for Mere Mortals:
http://www.amazon.com/dp/0201752840?tag=viescaconsulinc
John Viescas, author
Microsoft Office Access 2010 Inside Out
Microsoft Office Access 2007 Inside Out
Building Microsoft Access Applications
Microsoft Office Access 2003 Inside Out
SQL Queries for Mere Mortals
http://www.viescas.com/
(Paris, France)
-----Original Message-----
From: MS_Access_Professionals@yahoogroups.com
[mailto:MS_Access_Professionals@yahoogroups.com] On Behalf Of Allen Bennett
Sent: Wednesday, October 05, 2011 12:19 AM
To: MS_Access_Professionals@yahoogroups.com
Subject: RE: [MS_AccessPros] New Member
There is a list of tasks, of which not all clients have to do all the tasks,
and the caregivers check off which tasks that that particular client has
done.
Are you saying that a good database design should use an id number of some
sort in only two tables, and, if necessary, a table should use two (or more)
different ID numbers?
I guess I'll have to get your book (Microsoft Office Access 2007 Inside
Out), but, judging from the reviews on Amazon, I doubt that I could make
heads or tails of it.
Thanks for your help. Hopefully, I can eventually get what you're talking
about through my thick head!
Allen J. Bennett
From: MS_Access_Professionals@yahoogroups.com
[mailto:MS_Access_Professionals@yahoogroups.com] On Behalf Of John Viescas
Sent: Tuesday, October 04, 2011 11:44 AM
To: MS_Access_Professionals@yahoogroups.com
Subject: RE: [MS_AccessPros] New Member
Allen-
And what happens when you add the 16th task? You should never design a
"repeating group" in a database table - that's what the 15 boolean fields
are.
You should have a separate row for each task for each client. Do all clients
to
all tasks? If some do only some of the tasks, a table that has a row per
task
per client makes more sense. See my proposed design with the third table to
actually define the tasks.
John Viescas, author
Microsoft Office Access 2010 Inside Out
Microsoft Office Access 2007 Inside Out
Building Microsoft Access Applications
Microsoft Office Access 2003 Inside Out
SQL Queries for Mere Mortals
http://www.viescas.com/
(Paris, France)
-----Original Message-----
From: MS_Access_Professionals@yahoogroups.com
<mailto:MS_Access_Professionals%40yahoogroups.com>
[mailto:MS_Access_Professionals@yahoogroups.com
<mailto:MS_Access_Professionals%40yahoogroups.com> ] On Behalf Of Allen
Bennett
Sent: Tuesday, October 04, 2011 8:34 PM
To: MS_Access_Professionals@yahoogroups.com
<mailto:MS_Access_Professionals%40yahoogroups.com>
Subject: RE: [MS_AccessPros] New Member
John,
I'm using Access 2007. I'm not sure how to import the design of the table
in here-but, in the second table, I have the client number, 15 tasks as
Boolean fields, and a date. Am I TOTALLY off-base as to my design? As you
probably can tell, I am pretty new to database design.
Allen J. Bennett
From: MS_Access_Professionals@yahoogroups.com
<mailto:MS_Access_Professionals%40yahoogroups.com>
[mailto:MS_Access_Professionals@yahoogroups.com
<mailto:MS_Access_Professionals%40yahoogroups.com> ] On Behalf Of John
Viescas
Sent: Tuesday, October 04, 2011 10:17 AM
To: MS_Access_Professionals@yahoogroups.com
<mailto:MS_Access_Professionals%40yahoogroups.com>
Subject: RE: [MS_AccessPros] New Member
Allen-
Which version of Access are you using? If 2007 or later, you should consider
doing this entirely in Access - you can obtain free software to create an
install package for the user that works even if they don't have Access.
To answer your question, I would need to see the full design of the second
table. I trust it looks like:
ClientID (Pkey field 1)
TaskID (Pkey field 2)
DateEntered
DateRequired
You probably should have a third table to describe the tasks:
TaskID (PKey)
TaskTitle (text - short description)
TaskDescription (memo)
John Viescas, author
Microsoft Office Access 2010 Inside Out
Microsoft Office Access 2007 Inside Out
Building Microsoft Access Applications
Microsoft Office Access 2003 Inside Out
SQL Queries for Mere Mortals
http://www.viescas.com/
(Paris, France)
-----Original Message-----
From: MS_Access_Professionals@yahoogroups.com
<mailto:MS_Access_Professionals%40yahoogroups.com>
<mailto:MS_Access_Professionals%40yahoogroups.com>
[mailto:MS_Access_Professionals@yahoogroups.com
<mailto:MS_Access_Professionals%40yahoogroups.com>
<mailto:MS_Access_Professionals%40yahoogroups.com> ] On Behalf Of Allen
Bennett
Sent: Tuesday, October 04, 2011 6:57 PM
To: MS_Access_Professionals@yahoogroups.com
<mailto:MS_Access_Professionals%40yahoogroups.com>
<mailto:MS_Access_Professionals%40yahoogroups.com>
Subject: [MS_AccessPros] New Member
I'm writing a VB6 program with an Access database, and I've never worked
with Access with more than a single table. This is a program for ADL
(Activities for Daily Living), and I thought it would be nice to have the
functionality of clicking on a date that the tasks were changed, so that, if
the daily tasks were changed (three months down the road, maybe), you could
see the basic progress of the client. At the moment, I have two tables-one
with the client number, and the name, address, etc., and a second table with
the client number, the tasks required, and the date. If I do add the
functionality for looking up when the tasks required are changed, would I
need a third table, and, if so, what fields would be necessary in it, and
how should it be linked to either (or both) of the other tables. At this
time, I don't want to ask the owners of this business what they want this to
be like, as I am a client (no one likes to admit they need caregivers, do
they???!!!???) doing this on my own, and I'd like it to be a surprise.
Thanks for any help,
Allen Bennett
[Non-text portions of this message have been removed]
------------------------------------
Yahoo! Groups Links
[Non-text portions of this message have been removed]
------------------------------------
Yahoo! Groups Links
[Non-text portions of this message have been removed]
------------------------------------
Yahoo! Groups Links
Tidak ada komentar:
Posting Komentar