Does this make sense?

  • Thread starter Thread starter Jane
  • Start date Start date
J

Jane

Hi

I am new to Access programming and I would appreciate a
bit of help with the following.

I am doing a db for a company with part-time staff and
full-time staff. For all staff they need things like
name, address and telephone number. But for full time
staff they also need DOB, mother's maiden name and to tick
a box to say they are on the mailing list. For part-time
staff they only need the hourly rate and the cell phone
number.

Does the following make sense?

tblAllStaff (with name, address, phone)
tblFullTimeStaff(with DOB, mother's maiden name and
mailing list)
tblPartTimeStaff(hourly rate, cell phone number)

The first table will have the built-in automatic number as
the unique identifier, which is then used by the other two
tables (which are linked to tblAllStaff by a one-to-one
relationship).

I'd be grateful for any help.

Jane
 
Hey Jane,

Makes perfect sense to me, except that you posted a table question to
a specifically-named "forms" group ;-)

The only thing I might think about, is the total number of employees
now and in the projected life of the company: if it's small (< 100?),
you could probably just create one table with all that data.
HOWEVER, I will qualify that statement by saying that the MVP's among
us would probably disagree, and say that your original design is just
right!

Matt
 
Your design should be fine, but note that, if a staff member moves from
full-time to part-time, or vice-versa, you'll need to delete from one table
and append to the other table. Additionally, if you decide that a part-time
staff member now should have the option of being on the mailing list, etc.,
then you will have to redesign your tables to either duplicate that field in
both tables, or delete it from the full-time table and add it to the All
table.

It might be easier to have one table, with a boolean field for PartTime
(Yes/No). That way, you'd just need to toggle that field as statuses change;
and you'll always have access to all the possible options for a staff
member, even if you don't use them for some.
 
Thanks very much everyone. I feel a lot more confident
now.

Jane
-----Original Message-----
Hey Jane,

Makes perfect sense to me, except that you posted a table question to
a specifically-named "forms" group ;-)

The only thing I might think about, is the total number of employees
now and in the projected life of the company: if it's small (< 100?),
you could probably just create one table with all that data.
HOWEVER, I will qualify that statement by saying that the MVP's among
us would probably disagree, and say that your original design is just
right!

Matt
Click to expand...
 
To be safe, you might want to take it one step further and use an emp_status
field instead of a boolean. That would allow you to accomodate additional
categories, such as consultants.

--
Allan Thompson
APT Associates/ FieldScope LLC
MS Office Automation / Measurement and Reporting Systems
www.fieldscope.com
860.242.4184
 
Allan Thompson said:
To be safe, you might want to take it one step further and use an emp_status
field instead of a boolean. That would allow you to accomodate additional
categories, such as consultants.
Click to expand...
I'm glad I read this before saying the one table with a Boolean field was
the best idea.
 
Back
Top