howdy folks,
i been searching all over the forum for answers to my question, but i'm still a little fuzzy on setting my dbase up for multi-users so here goes. i would like to have my dbase located on the shared drive on an NT server and have multiple people be able to view the dbase at the same time, but not edit or change the design, code, objects,...etc in any way. multiple users must be able to view the same object (e.g. report, form,...etc) at the same time. i'd also like to set a password that allows a user administrative priviledges once they have logged in. i've read that using the database splitter is one option for this, and i've also seen people do it by just creating custom menus and not giving users the option of editing any of the objects. i'm wondering what people's thoughts are for my situation where users will only have read only access to the dbase. many thanks to all for any suggestions.
i been searching all over the forum for answers to my question, but i'm still a little fuzzy on setting my dbase up for multi-users so here goes. i would like to have my dbase located on the shared drive on an NT server and have multiple people be able to view the dbase at the same time, but not edit or change the design, code, objects,...etc in any way. multiple users must be able to view the same object (e.g. report, form,...etc) at the same time. i'd also like to set a password that allows a user administrative priviledges once they have logged in. i've read that using the database splitter is one option for this, and i've also seen people do it by just creating custom menus and not giving users the option of editing any of the objects. i'm wondering what people's thoughts are for my situation where users will only have read only access to the dbase. many thanks to all for any suggestions.
