Well, I spend some time looking at your dB..... there are things I think will cause you headaches later.
EVERY module should have these two lones at the top:
Code:
Option Compare Database
Option Explicit
In your code you are using
Code:
dTotalSize = Form_frmProgressMeter.txtBack.Width
Form_frmProgressMeter.bxBack.Width = 0
to refer to a form. This is not the proper way. It is internally how Access refers to forms, but you cannot use it to refer to forms.
The proper method is "Forms!frmProgressMeter"
Don't use spaces in object names (fields, queries, forms or reports)
I think you need work on your table structures. You have "tblTechs" PK field linked to "tblSites" PK field. This is a one-to-one relationship. I think it should be a one-to-many or a many-to-many relationship.
one-to-many: One Tech can be assigned to many Sites and one Site has one Tech.
many-to-many: One Tech can be assigned to many Sites and one Site can have many Techs.
Which of the above two lines is true?
I added a table for "Skills and Certifications" and a junction table. I removed "CCNA", etc from the Techs table... "CCNA" is data, not a field name.
Why a table?? Like you have the table design, if you wanted to add another Skill/Cert, you would have to modify the Tech table, then the queries, then form(s), then reports(s). A lot of work just to add 1 Skill/Cert....
With a table, you just add another record.. Plus you have the option of adding expiration dates.
I realize I don't know anything about your requirements, but this is what I came up with (it is a start - still needs more work):