Re: Linking Forms

John,
I'm trying to basically do the same thing and Im having problems getting the
forms to link. I have a table with the following fields:
Case#
Date
Time
Location
I would like to open a new form with a button such as a witness table with
the following fields:
Case Number
Witness Name
Address
Phone
Ect.

I would like the forms to link by the case number and act like a subform.
Can you help? Kinda new to access and don't know much about coding. I can't
use a subform because I'll have several other tables i want to link such as
suspect table, vehicle info, images, arrest table and more. I didn't think it
would be good to create one large table? or would it?

Thanks

"John W. Vinson" wrote:

On Tue, 14 Oct 2008 10:21:01 -0700, sd2352 <sd2352@xxxxxxxxxxxxxxxxxxxxxxxxx>
wrote:

I recently built an employee database using one large table and multiple
forms.

That is the source of your problem. You're not using Access as it is designed
to work!

Each form has 3 common fields: SSN, Employee's first and last name. My
problem is when I enter a record into the first form, then click to the next
form, it doesn't stay on the same record. How can I get my forms to link
together so if I'm working on one specific employee record, it will stay on
that record when I switch to another form?

The forms I created include: General Info, ER Contacts, Benefits, Salary Hx,
and Termination. When I enter info into the General Info form then open the
ER Contacts form, I have to search again for the record I was just working
on, it doesn't automatically pull it up. Is there anyway to program Access to
pull up the SAME record in real time?

If you insist (very unwisely IMO) on using one grand master table as a
spread*** for all this information (much of which should be pulled out into
related tables), then consider using one Form with a Tab Control. This will
let you open a record and then go to various tab pages for specific data.

I'm assuming that one employee will have multiple ER Contacts, multiple
benefits, certainly multiple records of salary history... shouldn't there be
one to many relationships between the employee record and related tables for
this information?
--

John W. Vinson [MVP]

.