I seem to remember getting an error similar to this (can't remember if was the same messge) when we rolled out an MS Database over a network. Users on one part o fhte network were OK, on the other part they couldn't see the tables (database was split front and back end).
I had to look into the netwokr issues involved, find the solution, and then explain to our useless IT Support Manager how to fix the problem (only his department had the right permissions to effect the solution).
It is sometimes worth remembering two things:
a) MS Access can be affected by network issues.
b) It's always worthwhile putting someone in charge of IT Support who, in technical terms, can do more than just barely turn a computer on!