Weird Issues on some pcs after deploying

[Dazzy]

Hey Guys

I recently deployed our new database onto PC's in the main admin area, out of 8 machines it works fine on 6 but on the other 2 there are different issues.

On one machine the girl cant login to the database, for some reason it doesn't seem to be picking up the username correctly from the computer and is showing as ?name. Typing in the username doesn't help either.

On the other machine the girl can login to the database fine, but opening most area's causes Access to freeze and crash.

Since it's working fine on 6 pcs in the main admin fine and 3 more in another area I am thinking its a problem with the individual machines.

All machines are running Access 2010.

Has anyone any incline?

Thanks

Gary

 

[Dazzy]

Hey

No there is no wireless devices on the LAN currently.

What I found with the girl who couldn't login, was there was a number of library references missing in VBA, resulting in none of the modules being available.

I added the references back in but it didn't fix it (I couldn't do a reboot yesterday as she was in the middle of the wages so will check on Monday as I don't work today.)

The other pc has all the right references, but still cant fathom why it's crashing on Access when you open certain areas of the DB.

 

[Dazzy]

Managed to solve the freezing problem, was related to some HP security software that shipped with the PC.

But still cant fathom why the other one cant load modules.

 

[Dazzy]

The error the pc that cant load the modules is giving is

the module name is misspelled or refers to a module that doesn't exist

However that would indicate the frontend is corrupt, however the exact same file works on all the other pc's when copied to the local machine.

Anyone any idea why one computer would suddenly start to show this message, the database worked fine when I gave the staff a preview version to look at a few weeks before deploying.

Any help would be great.