Works on 2 computers but not a third?? Can't find macro error!

[coloneldecker]

I have an access database stored on a shared drive. It works for me in my office, it works for another user in a second office. However a third user who works in the second office keeps getting a "can't find the macro" error whenever they attempt to do anything and I have no clue why. Anyone got anxiety why it works fine for everyone except this guy who is accessing the exact same database?

 

[bob fitz]

Have you split the database into a single backend and put the frontend on each users computer

 

[coloneldecker]

It's just the database sitting in a shared drive and everyone accesses it from there. I have developer access and the other two don't but they use/access it the same way from the same office and one user is working fine and the other user is throwing up this error.

 

[bob fitz]

I would split the db as it should be for multi users.

 

[coloneldecker]

For the moment I'm just trying to figure out why this error is occurring. I forgot to mention that the user accesses a second structurally identical database in the same manner and has no issues whatsoever.

 

[bob fitz]

For the moment I'm just trying to figure out why this error is occurring. I forgot to mention that the user accesses a second structurally identical database in the same manner and has no issues whatsoever.

Well, splitting the db may not help but as that is how it should be any way. Unless you try it you won't know if it helps.

 

[The_Doc_Man]

See if either or both of the following is true:
(1) The user with the error is running a 64-bit version of the Office package but the other users are not.
(2) The offending macro includes a step of type "RunCode" that triggers a function which contains a "RunMacro" VBA statement AND the user with the problem has a broken reference that ISN'T broken for the other users. (References are stored in the registry so they are per-user, not per-application.)

If neither of the above, then I don't know what could cause that.