On Tue, 12 Jan 2010 12:48:01 -0800, Jenn <(E-Mail Removed)>
wrote:
>I have the Employee and Software table setup. So in the Employee-Software do
>I add every piece of software each user has into this table? This is the
>table I was hoping to be able to merge the two tables together, so I didn't
>have to type each piece of Software into the Employee-Software table?
You don't have to type ANYTHING.
This is a perfectly standard and common many to many relationship. The
Employee-Software table has two key fields: the EmployeeID, a link to the
Employees table identifying who has this piece of software; and a SoftwareID,
identifying which software they have. There might be other fields if there is
specific information about *this* employee's copy of *this* software (e.g.
date installed, individual license information, version if that's not part of
your Software table).
You could use a Form based on Employees, with a Subform based on
EmployeeSoftware; you could have a combo box on the subform to select Access
2007 or Word 2003 or Zork I from a dropdown, storing that software's ID.
A very analogous situation can be seen in many sample databases; for instance,
in the Northwind sample database, there is a table of Orders, a table of
Products, and a similar resolver table called OrderDetails; it has fields for
the OrderID and the ProductID. Check it out there.
If you are thinking that you need to open table datasheets and enter data
there... *don't*. Tables are for data storage, forms for interacting with the
data. Check out Crystal's video and the other resources on these sites:
Jeff Conrad's resources page:
http://www.accessmvp.com/JConrad/acc...resources.html
The Access Web resources page:
http://www.mvps.org/access/resources/index.html
Roger Carlson's tutorials, samples and tips:
http://www.rogersaccesslibrary.com/
A free tutorial written by Crystal:
http://allenbrowne.com/casu-22.html
A video how-to series by Crystal:
http://www.YouTube.com/user/LearnAccessByCrystal
MVP Allen Browne's tutorials:
http://allenbrowne.com/links.html#Tutorials
--
John W. Vinson [MVP]