More than one - One to many relationships

[Jeep165]

I have a database that holds employee data. One table called Employees holds
the main information. I have two tables vacation time and uniform allowance.
These tables contain transactions concerning the employees uniform allowance
and vacation time balances.

In datasheet view I show the proper "+" sign showing the linked uniform
allowance table. It lists all the transactions for that employee just the
way I want. Works PERFECT. But when I go in and link up the new table
(vacation time) it replaces the subdatasheet uniform allowance. The common
field between the tables in EmployeeID.

Is this the way its supposed to happen or should I be doing something
diffrent? Can you have more than one...one to many relationships in a
database? I would think you could. But I don't think I'm doing something
right.

 

[Duane Hookom]

I set all subdatasheets to None. Use forms with subforms to display and edit
your records.

 

[Steve Schapel]

Jeep,

Yes, you can have more than one 1-to-many relationship, in fact this is
very common. What you are referring to is more a limitation with
datasheets. As a "rule of thumb", think of tables as out of bounds, and
not fit for human consumption, except in the design, development, and
debugging phases of your application. In the production phase, all data
manipulation should be via properly constructed forms, and in this case
forms and subforms. And in the case of subforms, you will find
continuous view has a lot of advantages over datasheet view.