data entry not valid

[jzwp22]

I did some quick testing regarding linking the subforms using both EmpJobsID and GrpJobTitleID. It will not work correctly. Linking via only the EmpJobsID will work fine. The amended frmCEmps2 is included in the attached DB.

 

[sunshine076]

Thank you for your help to all. I do have one other question that I dread to ask and that is when we (jzwp22 and I) created reports back in April I have them all formatted properly with my old EmpJobs form. How hard would it be to convert them to the report layout? If needed I can attach some of my reports

 

[jzwp22]

Reports are based on either tables or queries, not the forms. If the reports still give you the correct data then there would not be a need to change them.

 

[sunshine076]

Reports are based on either tables or queries, not the forms. If the reports still give you the correct data then there would not be a need to change them.

Although they give me the proper data I am receiving an entry that says enter in parameter for tblempjobquals.empjobquals what does this mean?

 

[jzwp22]

When a query prompts you for a value it is either an intentional parameter (for which you designed) or it means that the query cannot find the indicated field. This can mean several things: the field name is misspelled or the field name was somehow changed after the query was created.

 

[namliam]

But the key is to know when they are useful and when they are not.

Exactaly!

This is the point, they are good in some cases but ... you have to know when / where and how to use them.
I have seen forms with 10 DLookups on 1 table, then a DLookup to make a join and another 3 DLookups of the join, question put to me: Why is this database so slow...

DUH !

DLookups should be off limits unless it is only 1 Dlookup on 1 table any further DLookups usually your better off doing a select.

 

[sunshine076]

I've attached a stripped down version of your database with a new form frmCemps (and associated subforms) that illustrates what I was describing in my earlier post.

JZWP22 since I have worked with you before is there a way to change the required training table and add that to a combo box and still have everything show on the report?

 

[jzwp22]

I'm not sure I quite understand your question. Can you be a little more specific? It sounds like you want to add a combo box (to a form?) based on the training table somewhere and have it display on a report (which report?).

 

[sunshine076]

What I am going to do is instead of entering in an ID number for each of the training form in the upper right hand corner I plan to use a drop down menu for each entry and have them all show in that box. Right now I have over 200 training topics that we use and it would make it easier to have a combo box to store all this information and then in the report Training Required I would also want it to show what they are trained in with their date. I hope this helps

 

[jzwp22]

In general, you should be able to use a combo box instead of a textbox. You want to make sure that the bound field of the combo box is the ID field. The only thing that concerns me is that the ID is in the upper right corner of the form. Is the form bound to another form via that field? If you cannot post the database can you post a screen shot of the form in question?

 

[sunshine076]

I plan to keep it how we have it setup. However, my only additional question is that when we set this database all up and added the cross trained section. It isn't allowing me to save the dates for the cross trained or see the job description.

 

[jzwp22]

If you have some 200 training topics, they should be in a table and then you can populate the combo box using the table the holds the topics. I guess I really need to see your database at this point to be able to help you further.

 

[sunshine076]

The section that I am talking about is for actual training which I don't need the combo box. I am able to create the cross train but it won't allow me to enter in dates.

 

[jzwp22]

It is hard to help without seeing the actual database and form, but I am guessing that if the form is based on a query that joins several tables, you might have created an un-updateable recordset.