As Alex suggested earlier, why can't you just set the remote DMs to the "view only" type in the dmcfg file (which disable omsets) and then use the environment files and their associated passwords to renable omsets for any users that need to have them? That's the way we do it. I have one unix box setup to serve remote foxviews, the dmcfg is configured to make them "view only", the environment that starts up maintains that and then if anyone needs more access they have a password to get into a more secure environment that re-enables omsets and such. Is there a reason this method would not work for you? -- Jeremy _______________________________________________________________________ This mailing list is neither sponsored nor endorsed by Invensys Process Systems (formerly The Foxboro Company). Use the info you obtain here at your own risks. Read http://www.thecassandraproject.org/disclaimer.html foxboro mailing list: //www.freelists.org/list/foxboro to subscribe: mailto:foxboro-request@xxxxxxxxxxxxx?subject=join to unsubscribe: mailto:foxboro-request@xxxxxxxxxxxxx?subject=leave