runtime in a multiuser environment

[hollyylloh]

I have a database split into a frontend and a backend. I am using Office 2003
developer extensions. I have created both a server side installation and a
client side installation with the packaging wizard. When I include the
runtime with the package and set the desktop and start menu shortcuts to open
the application using the runtime, I get a sharing error. The error says the
the backend.mdb is in use when I try to open the application on more than one
client at the same time. If I do not use the runtime but instead open the
application with a full version of access, I do not have this problem. So
then the question is, may the runtime version be used in a networked
environment? Is this behavior by design or is there a setting or switch that
will allow multiple runtime versions to access the backend.mdb at the same
time. Thank you for your help.

 

[Chris O'C via AccessMonster.com]

The Access runtime can be used in a multiuser environment. Look at the start
menu shortcuts. Do they have the /excl switch? Don't use that switch for
the shared backend. Check the db file options. Default open mode should be
shared, not exclusive, for the backend.

If it's already shared, post the Windows permissions on the folder holding
the backend for the first user who opened/linked to the backend, then post
the Windows permissions for the user who is blocked.

Chris

 

[hollyylloh]

Chris, thank you. It is now working. I checked if the /excl switch was used
and it was not. Then I check the permissions on the backend file and
containing folder. I think where I went wrong is that I just set permissions
on the backend file and containing folder to just allow everyone full access.
When I went in and setup permissions for specific users I quit getting the
sharing violation error. If you don't mind, why did full access permissions
to everyone not work? Thanks again.

 

[Chris O'C via AccessMonster.com]

It means 1 or more users didn't really have full control permissions. When
you manually set users' permissions, you gave more permissions than those
problem users originally had. That's why I asked you to list the permissions
for the first person who opened/linked to the backend and the permissions of
the person who was blocked. One or both didn't have enough permissions.

It's better to set up permissions for a group and then add members to the
group. Lot less work.

Chris

 

[hollyylloh]

thanks Chris

It means 1 or more users didn't really have full control permissions. When
you manually set users' permissions, you gave more permissions than those
problem users originally had. That's why I asked you to list the permissions
for the first person who opened/linked to the backend and the permissions of
the person who was blocked. One or both didn't have enough permissions.

It's better to set up permissions for a group and then add members to the
group. Lot less work.

Chris