Why does this happen to the access db in a mu environment? I have an app
running with security enabled (Access 2003 fe/be) I have followed the advice
I uncovered in this newsgroup that is to uncheck Auto Correct, add persistent
connection and a number of other suggestions but still two users cannot be
logged in at the same time and the problems is sporadic - for almost two
weeks it ran without any problem and for the last three days the lock files
have been locking up and a server reboot is needed. Prior to the two weeks
there was a run where it would lock up and then work fine.
The shortcut has a switch for the wrkgrp file which points to the mdw on the
network (same folder as the be) and when a user exits, code redirects the
wrkgrp file back to the default this way security is only used for this app
and if there are other access db's the user is using it won't prompt for
login unless the default security is enabled.
My wonderment is does this have to do with object ownership? The default I
believe is admin. Would it matter if I set up the program as a regular user
on the network or should I have loaded the program as an admin (no set up
install as of yet)?
Thanks much for any light you can shed on this?
Manny
david@epsomdotcomdotau - 27 Sep 2007 11:08 GMT
What kind of server are you using? Is it fully patched?
(david)
> Why does this happen to the access db in a mu environment? I have an app
> running with security enabled (Access 2003 fe/be) I have followed the advice
[quoted text clipped - 16 lines]
>
> Manny