Simple Form Filter

SubMatrix

New member
Local time
Today, 15:48
Joined
Jan 10, 2009
Messages
8
I have a form that tracks employee training. I have one form that is used to add training records (which works fine) and another for updating/deleting records (which is causing me problems). In the form, I have the attribute "empName" located in the form header. In the detail section, I have the attributes "courseName", "compDate", and an attachement box for uploading a certificate if applicable. The "empName" attribute is a drop-down box that references the employee roster table.

What I want is for the user to be able to select a name from the "empName" drop-down box, and then have all the (training) records for that employee be displayed in the detail section. I have fooled around unsuccessfully with the Me.Filter code in the After Update property of empName but I do not even know if this is the right approach to take.

Any help would be greatly appreciated.
 
The wizard for creating a subform should walk you through the process.

I would question why you need a seperate form to add records and another form to update and delete records. You should be able to do it all with just one form.
 
Is there a way to do it without a subform? For one, the attachment field doesn't seem to work correctly in a subform, it breaks it down into like five different parts. Secondly, the little bit I did get working displays all the records in a visually traditional form view which while functional, isn't as attractive as what we created.

As for splitting the forms is because of access controls. There will be multiple front-ends. One person will only be responsible for entering training records but should not have access to view/edit/delete other records while someone else will be in charge of editing/deleting records.

I have done this before so I know it's possible, I just can't remember the code to use. By using the Me.filter I can get it to work somewhat but unless I follow a specific route it will error on me, and since it will be used by non-access savvy users, it needs to be as error-proof as possible.
 

Users who are viewing this thread

Back
Top Bottom