Question regarding Modules

  • Thread starter Thread starter Lis'a
  • Start date Start date
L

Lis'a

Good afternoon:

I have three tables that have a one-to-one relationship.
The primary table position contains job information and
it uses an existing primary key that contains unique data
that is input by the user. This field is linked to the
personnel table using this field. When the user adds a
new record into the position table and then wants to add
a person to that position, I need to capture the primary
key and append it to the position table. I'm using the
tab control feature in the forms object so the user can
can tab between information. I've tried several different
approaches but all are very cumbersome. If anyone has
any suggestions or recommendations I would greatly
appreciate it.

Thanks in advance.
 
Good afternoon:

I have three tables that have a one-to-one relationship.
Click to expand...

Ummm... why? One to one relationships are QUITE uncommon; they're used
for Subclassing and for certain types of security getarounds. What are
these tables?
The primary table position contains job information and
it uses an existing primary key that contains unique data
that is input by the user. This field is linked to the
personnel table using this field. When the user adds a
new record into the position table and then wants to add
a person to that position, I need to capture the primary
key and append it to the position table. I'm using the
tab control feature in the forms object so the user can
can tab between information. I've tried several different
approaches but all are very cumbersome. If anyone has
any suggestions or recommendations I would greatly
appreciate it.
Click to expand...

By far the simplest way is to use a Form for the first table into
which data will be entered, and Subforms for the related tables. Use
the ID as the master/child link field and it will fill in
automatically.
 
Theses tables are for our HR department. The have an
existing ACCESS program that is currently causing
problems because it has never been reworked since 1997
and has been modified but never analyzed. Pieces have
been added to extract data by adding fields and all types
of craziness (including mega redundant data).

I agree, one-to-one relationships are quite rare, one-to-
many relationships are quite common. The table structure
is:

Position (Jobs within the organziation)
Personnel (Employees relating to that Job)
Security (Security clearance information pertaining to
the employee)

There are many positions but only one employee to a
position(job). The position table provides vacancy
information for our organization.

Thanks!
 
Position (Jobs within the organziation)
Personnel (Employees relating to that Job)
Security (Security clearance information pertaining to
the employee)

There are many positions but only one employee to a
position(job). The position table provides vacancy
information for our organization.
Click to expand...

Did the Subform approach give you the desired result?
 
Back
Top