SandyMcc, Access makes it very easy to create a bad database. What you can end up with is something that you will always be coming back here to try and get fixed one way or another. To support complex functions (and most business applications are complex) requires a lot of know how if you want to keep others from thinking that you don't know what you're doing. Be warned that there is a big learning curve if you want it to work properly without a lot of hacking.
You need to worry about
- what autonumber fields are not
- primary and foreign keys
- entity/attribute relationships and understanding normalization
- what not to have in object names plus what words you should not use in names
- why to not use calculated fields or multivalue fields
- not keeping objects (files) inside an Access database
- how queries work and when to use what type
- how reports group and sort
- etc, etc, etc.
and then if you want the db to be robust, you need to learn some vba code or else you're at the mercy of macros and what happens when they fail. Not saying you should not learn - just be aware that you can't rush this if you want to shine.
On another note, I can't help but wonder if you're not running the place, then why bang your head against the wall trying to move someone who can't be persuaded? Sure, you can see a better way and maybe at not much cost. However, one thing I learned during 40 years in the workplace is that if those who make the decisions can't be convinced of a need, then banging my head against the wall will only hurt me. In that case, they get the best I can do with what resources they give me.
The more we hear silence, the more we begin to think about our value in this universe.
Paraphrase of Professor Brian Cox.