adding course-information to a business database

[Wouter]

I created a simple database for my business (it includes names, birthdays,
etc.). Now I created a new database with includes course information about my
employees. therefor i created 3 databases. 1 coursename, 2 employee name and
a table that combines table one and to by a 1 to many relation. What i want
to achieve is using the names of the simple database and combine database one
and two by a query in a form. In this form I want to see by person first of
all his/her genaral data and secondly the course he/she has to follow. I do
not no how I have to create the relations, the query and the form...

 

[John W. Vinson]

I created a simple database for my business (it includes names, birthdays,
etc.). Now I created a new database with includes course information about my
employees. therefor i created 3 databases. 1 coursename, 2 employee name and
a table that combines table one and to by a 1 to many relation. What i want
to achieve is using the names of the simple database and combine database one
and two by a query in a form. In this form I want to see by person first of
all his/her genaral data and secondly the course he/she has to follow. I do
not no how I have to create the relations, the query and the form...

Do you mean teo *databases* or two - or three - *tables*? A Database, in
Access jargon, is the .mdb or .accdb container for multiple tables, forms,
reports, etc.

A course enrollment database is a classic case of a many to many relationship.
Each employee may take zero, one, or many Courses; each course will be taken
by zero, one or many Employees. The proper table structure needs three tables:

Employees
EmployeeID <primary key, some unique identifier such as an autonumber or
employee number>
LastName
FirstName
<other biographical data>

Courses
CourseNo <manually assigned or autonumber unique identifier>
CourseName
<other fields describing the course>

Enrollment
EmployeeID <link to Employees, who enrolled>
CourseNo <link to Courses, what course they enrolled in>
<other information about this employee in this course, e.g. date enrolled,
comments, yes/no field for satisfactory completion or a grade field>

Note that the employee name exists ONLY in the Employees table; the coursename
exists ONLY in the Courses table. The enrollment table contains only links.
You would have a one to many relationship from Employees to Enrollment joining
on EmployeeID, and another one to many from Courses to Enrollment by CourseNo.

Take a look at some of these resources for more information:
Jeff Conrad's resources page:
http://www.accessmvp.com/JConrad/accessjunkie/resources.html

The Access Web resources page:
http://www.mvps.org/access/resources/index.html

A free tutorial written by Crystal (MS Access MVP):
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