D
DavidUp
I have recently set up a multiuser database with a front end on each users
workstation and the back end on the server. All users are forced to use the
front end in Access 2007 Runtime mode.
The system has been tested for several weeks and worked fine in a branch
office where all users are at administrator level.
When I transferred the database to our head office I discovered that
standard users (i.e users, mobile users or power users) receive a warning
message that the database has been opened in read only mode.
Whilst these users are able to edit most of the data on the forms and
queries they are prevented from adding or editing hyperlinks which is
necessary to access clients' folders on the servers.
The strange thing is that this only happens when we force users to use their
locally stored front end. If a user finds their way to the master front end
stored on the server the database opens without any restrictions as to which
fields can be edited.
Needless to say for security and network traffic reasons we do not want all
users accessing the front end on the server.
Both servers are running under Server 2003 and all workstations are Windows
XP.
Has anyone got any ideas please?
workstation and the back end on the server. All users are forced to use the
front end in Access 2007 Runtime mode.
The system has been tested for several weeks and worked fine in a branch
office where all users are at administrator level.
When I transferred the database to our head office I discovered that
standard users (i.e users, mobile users or power users) receive a warning
message that the database has been opened in read only mode.
Whilst these users are able to edit most of the data on the forms and
queries they are prevented from adding or editing hyperlinks which is
necessary to access clients' folders on the servers.
The strange thing is that this only happens when we force users to use their
locally stored front end. If a user finds their way to the master front end
stored on the server the database opens without any restrictions as to which
fields can be edited.
Needless to say for security and network traffic reasons we do not want all
users accessing the front end on the server.
Both servers are running under Server 2003 and all workstations are Windows
XP.
Has anyone got any ideas please?