|
security
newsgroups
|
|||||||||||||||||||||||
|
|||||||||||||||||||||||
MDW deployment?Hi again! I have created a front-end and a secured backend. I have also
created a synchronized (auto-update) platform where every user will get the latest front-end version on their local machines. However, I'm unsure whether I should also distribute the MDW (security) file. It was suggested to me to distribute copies of the front-end to avoid some data corruption. I think that makes sense (besides the hassle of keeping everybody up to date with the latest front-end version). However, I'm unsure whether or not distributing a copy of the MDW file as well. I would prefer to keep on the network but do not know of any caveats, pros, cons. What do you guys recommend?!
Show quote
Hide quote
"John" <noem***@noemails.mail> wrote in message Putting it in a network folder will be fine.news:f2QLg.3717$QM6.3518@bgtnsc05-news.ops.worldnet.att.net... > Hi again! I have created a front-end and a secured backend. I have also > created a synchronized (auto-update) platform where every user will get > the latest front-end version on their local machines. However, I'm unsure > whether I should also distribute the MDW (security) file. > > It was suggested to me to distribute copies of the front-end to avoid some > data corruption. I think that makes sense (besides the hassle of keeping > everybody up to date with the latest front-end version). However, I'm > unsure whether or not distributing a copy of the MDW file as well. I would > prefer to keep on the network but do not know of any caveats, pros, cons. > What do you guys recommend?! > Keith. www.keithwilby.com It's a database. It contains user names, group names, and
associated security ID values. Like any database, you can share it, or make multiple copies. It's not used intensively: unless you are doing design changes (or those minor things like change the filter), you only look up your ID value once, when you log in. On the other hand, if it's not updated frequently, you can just distribute copies. You don't even need to distribute new copies to everyone: after all, you only need your own password. (david) Show quoteHide quote "John" <noem***@noemails.mail> wrote in message news:f2QLg.3717$QM6.3518@bgtnsc05-news.ops.worldnet.att.net... > Hi again! I have created a front-end and a secured backend. I have also > created a synchronized (auto-update) platform where every user will get the > latest front-end version on their local machines. However, I'm unsure > whether I should also distribute the MDW (security) file. > > It was suggested to me to distribute copies of the front-end to avoid some > data corruption. I think that makes sense (besides the hassle of keeping > everybody up to date with the latest front-end version). However, I'm unsure > whether or not distributing a copy of the MDW file as well. I would prefer > to keep on the network but do not know of any caveats, pros, cons. What do > you guys recommend?! > > Leave the mdw on the server. Passwords are stored in the mdw and you don't
want to overwrite someone's password when you distribute an updated mdw. -- Show quoteHide quoteJoan Wild Microsoft Access MVP John wrote: > Hi again! I have created a front-end and a secured backend. I have > also created a synchronized (auto-update) platform where every user > will get the latest front-end version on their local machines. > However, I'm unsure whether I should also distribute the MDW > (security) file. > It was suggested to me to distribute copies of the front-end to avoid > some data corruption. I think that makes sense (besides the hassle of > keeping everybody up to date with the latest front-end version). > However, I'm unsure whether or not distributing a copy of the MDW > file as well. I would prefer to keep on the network but do not know > of any caveats, pros, cons. What do you guys recommend?! Thank you all!!
John wrote: Show quoteHide quote > Hi again! I have created a front-end and a secured backend. I have also > created a synchronized (auto-update) platform where every user will get > the latest front-end version on their local machines. However, I'm unsure > whether I should also distribute the MDW (security) file. > > It was suggested to me to distribute copies of the front-end to avoid some > data corruption. I think that makes sense (besides the hassle of keeping > everybody up to date with the latest front-end version). However, I'm > unsure whether or not distributing a copy of the MDW file as well. I would > prefer to keep on the network but do not know of any caveats, pros, cons. > What do you guys recommend?! 
Other interesting topics
Security restrictions and table linking
Allow Help Desk to Reset Passwords Without Full Admins Permissions Necessary Permissions secured database Login in dynamically Drop Down on Table Lost My Permissions Securing the Back-End from mdb how to openForm a form in a referenced mde file Prevent all Access files from connecting to the same Workgroup? |
|||||||||||||||||||||||
