trying to create a database, need help!!!!!

[Guest]

Hello,
I am trying to make a database for all of our clients. The clients will
come from 8 different sites, I will need to get all demographic information
for each client, the dempgraphics for all members of the household, sex,
race, type of assistance, dollar amount of assistance, vendor. Do I need to
make a seperate database for each site, and then break it down further by
type of service and futher still by having a seperate database for the
household members (linked by client name to the client data base).

I need help with this, I am just learing Access and my boss thinks I will be
able to create a working database ASAP.

 

[storrboy]

Hello,
I am trying to make a database for all of our clients. The clients will
come from 8 different sites, I will need to get all demographic information
for each client, the dempgraphics for all members of the household, sex,
race, type of assistance, dollar amount of assistance, vendor. Do I need to
make a seperate database for each site, and then break it down further by
type of service and futher still by having a seperate database for the
household members (linked by client name to the client data base).

I need help with this, I am just learing Access and my boss thinks I will be
able to create a working database ASAP.

I get the impression that your boss is either one of the many who
think a database is a fancy spreadsheet, or the many who don't think.
If you are just learning, I can't recommend that you attempt this with
an ASAP time frame. You have many factors to consider in administering
a DB in multiple locations, and it dosen't sound like you've had much
experience designing tables or relationships. Without a lot of
assistance from an someone experienced, I think the best thing you can
do is pick-up one or more books on Access and start reading.

 

[Guest]

Hello,
That is what I am doing, reading to learn how to use this Access in the
first place.

 

[Bill Mosca, MS Access MVP]

JoAnn

You shouldn't need a separate database for each location unless there is a
physical reason (ie, no connectivity between sites and main office). All you
would need to keep sites separated is to give each site an ID. Use that ID
as a foreign key in all related tables.