SAVING EMPLOYEE ID DATA to TWO DIFFERENT TABLE FIELDS

[Holli]

Can't see the forest for the trees.



I have two tables that both contain the employee id field and two forms Combat System A (an auto populate combo box)
and Combat System B. The data entry information is then displayed in a report. The report is fine.
My problem is printing the report I would like the employee id field in Combat System A to auto populate in Combat System B.

Any help or suggestion would be greatly appreciated.

Thanks

Holli

[June7]

Doesn't make sense to me. What do you mean by 'an auto populate combo box'? What do you mean by 'auto populate' on report? What are the data relationships?

[Holli]

I have a drop down combo box (employee ID numbers) on form A that populates texts boxes; name, department, location and date. The user answers question on data entry form A then clicks the continue button,
(RunCommand acCmdSave Record)
Me. Requery
DoCmd. Close
Open Form B
then continues to answer the rest of the questions on Form B.
I would like for the user to be able to print their report. I can view the report by individuals put cant get it to print by individual id numbers.

Thanks

Holli

[June7]

Why are there two forms for answering questions?

Why can't you get it to print by individual ID numbers? Apply filter to report.

[Holli]

The survey is set up with 6 departments and I had to create Forms for each not enough space. . There are 368 questions with four different answers for each question (nightmare).

Thanks for your help.

Holli

[June7]

Did you consider putting forms on pages of a tab control?

Still don't know why there are two tables.

If you want to provide db for analysis, follow instructions at bottom of my post.

[Holli]

It is attached here.

Again sorry!!!

[June7]

I don't think you should link table A to table B to table C. These tables have a 1-to-1 relationship with tblEmployee. 1-to-1 relationship usually means a non-normalized data structure. A field for each question is not normalized structure. What if you need to add questions?

Multiple similar fields also indicates non-normalized structure. Multiple fields for GoToPerson means having to search 5 fields if you want to know which apps Chris Bigler can help with. These are also multi-value fields which I NEVER use.

Regardless of data structure you decide on, use form/subform arrangment. Tables A, B, C would be subforms on Employees main form. The subforms can be arranged on pages of a tab control. Form/Subform will synchronize saving the EmployeeID into related records. Otherwise, passing EmployeeID to new records of 'subform' opened as independent form will require code.

Questionnaire database has been topic of numerous threads - might search forum.

[Holli]

Thanks June 7

How would you address the to go person field (multiple value)? They want them to be able to select up to 3 individuals.

I know that the table structure is non normalized still fiddling with that. The data will be exported to excel. My biggest concern was allowing the end user to print their report once they take the survey.

Thanks for your help greatly appreciated.

Holli

[June7]

The alternative to multiple similar fields and multi-value fields is a related table.

Don't really understand issue with report. Use report/subreports arrangement. Main report bound to tblEmployee. Open report filtered to EmployeeID.

My preference is to pass value to report when opening by referencing a field/control of form. Example code to be in some event, such as button click:

DoCmd.OpenReport "report name", , , "EmployeeID=" & Me!EmployeeID

[June7]

Might review this http://www.rogersaccesslibrary.com/f...ey_topic3.html