I have been working on an Access Db for awhile and am very close to being ready to hand it over to the person who requested it. There will be one user and the db will reside on a desktop PC.
Here's my dillemma? How do I insure that the user will not have access to the tables? I'd hate for her to get curious and go in and "muck around" with the data. I have the db split and have logic to disable the "shiftkey bypass" on open. I plan to, also, convert the front-end mdb to a front-end mde. However, what do I do with the back-end (tables)? Is there a way to protect them?
I would like to keep the db split (front-end/back-end) so if modifications are required in the future (to the screens/reports/processing), I can just send her a new front-end (I have the 'relink' logic in place on initial launching of application).
Any ideas for protecting the tables?
Thank you.
Regards,
SueB
Here's my dillemma? How do I insure that the user will not have access to the tables? I'd hate for her to get curious and go in and "muck around" with the data. I have the db split and have logic to disable the "shiftkey bypass" on open. I plan to, also, convert the front-end mdb to a front-end mde. However, what do I do with the back-end (tables)? Is there a way to protect them?
I would like to keep the db split (front-end/back-end) so if modifications are required in the future (to the screens/reports/processing), I can just send her a new front-end (I have the 'relink' logic in place on initial launching of application).
Any ideas for protecting the tables?
Thank you.
Regards,
SueB