Search results

I think I will use this in the form BeforeUpdate Event to simply trap out any attempt to add an area that has already been assigned. Would you mind helping better understand this code? DCount("*", " AreaXEmployeeT", This will count all records in the AreaXEmployeeT. How does the rest work...

You could split the database and have one Front end for the Boss that has all the current functionality, and a second front end for everyone that is not the boss that only provides a form for the required data entry.

I'll have another look. I'm not sure how that helps as I need data from another table but, I'll check it out.

Sorry, you kind of lost me. Some times they are no longer on the list because they have moved on, other times they have been reassigned. I'm not sure what you mean by prefix non-eligible list members names. The table has only the foreign keys. and the query is really only processing foreign...

I appreciate your help, but the thread you linked really doesn't apply there is only the one combo box.

Well it is, the historic data is still there. But the query that filters out the non Area Security employees prevents the combo box from displaying it. Just to give you an idea of the volume we are dealing with there about 500 employees and about 30 are Area Security at any given time. They...

WOH, who woh.... Slow your roll ship mate. There is NOTHING wrong with the The Bee Gees. Robbie Williams, Take That, Cliff Richard, Kylie Minogue, Madonna, Cher and Michael Bublé Phil Collins. ya they can go. Especillay Madonna and Cher. But my dude DISCO.

Samual Adams is an Area Personnel Security Representative. This role is stored in the table EmployeeVitalDataT as a foreign key from the AuthorityGroupT table. Samuel Adams has vetted John Hancock and determined he has the proper clearance level and need-to-know to access area A. This is...

That's fair. Just trying to take in a lot of new VBA and tossing in SQL... It's a steep learning curve. If I implement #9 where does the code go?

No, no I totally understand, that's why I asked before I threw the file at you.

Would you be willing to have a look at what I have so far. I'll be up front my naming convention is a bit of a mess, still trying to get the hang of that. Also I am fairly new to Access and I'm operating outside my comfort box, which is good. If your comfortable your not learning.

Just to be clear this would be the control source for the combo box?

which of those do you think is the least complicated and most closely follow database normalization best practices?

Sorry EBS, I have a little experience with VBA, enough to where I'm not scared of it, and it tends to make sense to me. I have absolutely zero experience with SQL.

Doc, I noticed in another thread you were Navy. When did you serve?

No, that is not something that needs tracking. I do have fields for when the employee was granted access and who authorized the access, but once they are removed form a work area it is, for the purposes of this database, a non-issue.

Not sure what you mean by history. While I am not a fan of deleting records, I do fully intended on deleting records in the joining table to remove employees from areas.

A query may not be the best way to handle this. I have many employees who can potentially work in many areas and areas can have many employees. So we need a joining table. I want to use a combo box to assign the employees to the areas (saved in the joining table) that they are authorized to...