Access macros don't work over a shared network drive

[vanGogh]

I copied an Access application onto a shared network drive so that multiple
users on a peer-to-peer network could view data and run reports from the
application.

The generation of application reports are based on a Visual Basic function
created to generate and print appropriate reports from within the Access
application. A generic macro was created to call the VB function via the
RunCode macro action.

The application forms and data work properly when other users access the
application from the network drive. However, when a user attempts to click
on a menu item to generate a report, the user receives a Visual Basic error
stating that the code needs to be recompiled.

If I attempt to do the same thing on the machine where the application was
developed, the reports are generated fine with no VB compilation errors.

This behavior makes me believe that this problem is related to User and
Group Permissions.

I believe that the Access Admin user is associated with the local machine
where the application was created and this is the reason why the reports
aren't generated when the VB macros are called from another machine.

This is just a theory and even if my theory was true, I am not sure how to
get around this or fix the problem.

The general problem that I am running into is that there is no way to
authenticate and restrict network user access to this application because
there is no central domain controller being that this organization only has
peer-to-peer or workgroup network configuration. This is the reason why we
have to create a central network drive where the app has to be stored and
allow users on the network to get to the application via a shortcut on their
desktop.

If anyone out there has experienced these same types of problems or has a
solution that could possibly help me, please respond ASAP.

Any suggestions would be greatly appreciated.

 

[Norman Yuan]

No, the VBA code (or macro that contains VBA code, as you staed) is alway
run on local Access instance, although you place the Access application on a
shared network location. Every user has his own Access installed, right?
When a user start the Access app, the app itself in the said *.mdb/*mde file
is loaded into local machine's memory (data may not be entirely loaded into
local machine if the data amount is huge, though), and all code/macro is
executed locally. So, your problem could be related to that individual
computer. I'd check for missing reference first.