M
Marcos Serpas
I have a centrally located back-end database on a server. All users use an
MDE file that links to a secured.MDW file on the server.
If I make a change in security permissions using an MDE file on a local
computer, the changes only take effect on that particular computer.
If I login on another computer the changes I made do not take effect.
I've managed a way around this situation opening the original MDB file,
changing the security setting, compile the MDB, and distrubuting the new MDE
file with the updated settings.
Is this the norm? Why can't it the new security changes take effect by
using any of the MDE since they are all using the same MDW secured file?
Thanks.
ms
MDE file that links to a secured.MDW file on the server.
If I make a change in security permissions using an MDE file on a local
computer, the changes only take effect on that particular computer.
If I login on another computer the changes I made do not take effect.
I've managed a way around this situation opening the original MDB file,
changing the security setting, compile the MDB, and distrubuting the new MDE
file with the updated settings.
Is this the norm? Why can't it the new security changes take effect by
using any of the MDE since they are all using the same MDW secured file?
Thanks.
ms