When we first set up our database, we used the built-in User\nLevel Security. We wanted that because we had to use a\nsneaker-net to a remote office, and didn't want anyone there\nto accidentally destroy anything.\n\nAfter some problems with the remote user's not being able to\ndo what they needed, management made a knee-jerk reaction,\nand said to give the remote-office personnel full admin\npermissions to the entire db.\n\nAfter a few years of trouble-free use, management has now\nmade two decisions:\n\n1. To have our IT dept. set up the remote office front-end\nto link directly to our home-office back-end (instead of\ndoing manual, monthly appends at the home-office).\n\n2. Set up some sort of mechanism such that the\nremote-office personnel cannot alter records after a\nyet-to-be-determined amount of time.\n\nSince the remote office has a copy of the original MDW file,\nI'm assuming that I'll need to shift the mdb over to a\ndifferent MDW file. Is that correct?\n\nIf I'm on the right track here, can I just make a copy of\nthe existing MDW, rename it, open the mdb and use the\nWorkgroup Administrator to set the mdb to use the new MDW?\nThen alter the User/Group assignments to suit?\n\nThis is using MS Access 2002 on WindowsXP machines.\n\nIs my plan good?