data entry not valid

[sunshine076]

I had help with my database that was created and all of it works except for two cells that allow the user to enter in a date and if they are basic, advanced , or master qualified. I cannot post it because it is too big. Does it matter if it was originally created in Access 2000 and now used in Access 2003? This is due in a few days

 

[MarkK]

You haven't provided enough information about the problem!

...all of it works except for...

And it's unlikely that being created in 2000 and run in 2003 is a problem.
Cheers,

 

[sunshine076]

My problem is that I have several different forms on one document 3 of the 4 forms work. For my last form when you go and enter in a date and use the drop down menu for the basic, advanced, proficient it says invalid entry and it also says "invalid amount of data in field when I have only entered in one single number.

 

[boblarson]

How about posting a copy of the database here. We can probably do a quick "shake down" of it and have it back to you in a matter of minutes or hours, saving a lot of "back and forth" time.

 

[sunshine076]

I have tried to upload it but my zip file is too big for your website any suggestions

 

[boblarson]

I have tried to upload it but my zip file is too big for your website any suggestions

Quick questions -

1. Did you run Compact and Repair first and
2. Then did you zip it before trying to upload?

 

[sunshine076]

After a lot of cutting down I was able to get it to finally upload. The area that I am having my problem is the lower left corner. When you go and enter in a date and if it is basic, proficient, advanced it says invalid

 

[MarkK]

Lower left corner of what? There are 19 forms!

 

[sunshine076]

sorry about that the main form that I work off of is called tblemployees the individual form is called frm empjobs and tblempqualeval The table in the right hand corner doesn't allow any entries and I have more than the two employees each one has about 15-30 training elements that each have their own date. Before I expanding this db it was working and now it says that I have invalid entries.

 

[sunshine076]

When you click the field for dte Evaluation and go to enter in the date it says "the value you entered isn't valid for this field" and yet I haven't entered in any data

 

[boblarson]

I've been looking at it, but haven't been able to tell for sure what it is, but I think it has to do with a DIFFERENT field and NOT the date field. I think it may have to do with the Master/Child link of the subreport.

 

[sunshine076]

The version I have attached runs fine and the fields in question also work.You will also notice that I have made changes to the original format of the sheet. Is it possible that I messed something up or that I am using Access 2003 and this was originally created in 2000. However, is there a way to convert my current db to this one since it all works fine or do I have to start this one from where I left off.

 

[jzwp22]

Based on your relationships, the evaluation is tied to an employee's job qualifications which is in turn related to the employee's job title, but your form doesn't show the employee that you are evaluating. I think the main form needs to be based on the employee table (or a query that relates the employee to their job) and then the subforms should link from there

 

[jzwp22]

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.

 

[sunshine076]

Considering that each of my employees have different required training where would I put the description so that we know what they have been trained in? Would it go below the job quals number as a combo box?

 

[jzwp22]

You can add another textbox control to the form wherever you would like to put it and use the Dlookup() function that pulls the description based on the jobqualsID

 

[sunshine076]

Just making sure I have the right DLookup
DLOOKUP("[jobqualsID]","tblQualfication") from jswp22 reply

 

[namliam]

You dont use DLookup's in forms, you use subforms or a proper query to display your data !

 

[boblarson]

You dont use DLookup's in forms, you use subforms or a proper query to display your data !

I would disagree with that generalization. Domain aggregates can play a useful function (no pun intended) in forms. But the key is to know when they are useful and when they are not. For small dataset items, they can be just as fast (not as fast, but the timing would be imperceptible) as a query and subform. Plus, more forms, can mean more opportunities for corruption. Now if we were talking a LOT of records to wade through then you could have a point, but you can also use a query to pull only what you need for the Domain Aggregate and that can be as efficient as doing it the other way. If the query is only returning what you want (a single record) and is not searching down a bunch of records, then it can work just fine.

 

[jzwp22]

I have to agree with Bob on the use of the domain aggregate functions.

Sunshine076,

With respect to the DLookup() you will have to add criteria to get the correct qualification. I set up an unbound text box and used some code in the on current event to populate the description. The code uses the dlookup function. See frmCEmps in the attached DB.

With respect to namliam's response, you could use a properly constructed query to bring in the information as well, see frmCEmps2. I have some concerns with the query approach because you use several junction tables. This may cause some issues when trying to add new job titles to an employee using this form since it may result in an un-updateable recordset condition, but from what I remember from when I first helped you on this project, you were entering the job titles via other forms.

When creating the subforms for frmCEmps2, I realized that since an employee can have many job titles and that the titles are tied to job groups, I thought you might need to use a query as the record source for the frmCEmpJobs2 subform and link to its subform rmCEmpJobQual2 via both EmpJobsID and GrpJobTitleID. It might be best for you to do some testing with some example data to see if you need to join by both ID's