lock out design and layout views
- Thread starter krazieddi
- Start date
EternalMyrtle
I'm still alive
- Local time
- Today, 11:39
- Joined
- May 10, 2013
- Messages
- 533
You could save it as .accdr and have your users run it only in Runtime: available here http://www.microsoft.com/en-us/download/details.aspx?id=10910.
In runtime they will only have access to the final forms (no design/layout view , no navigation bar) so you need a switchboard and all forms will need to be accessible that way. You will need to think through the design and navigation which is a lot of extra work.
Runtime is especially effective if users don't have the full version of Access installed on their computers because any slightly knowledgeable person can change the file back to an accdb and open it in Access.
having said all that: you should also split the database and save the backend somewhere safe and just give users front ends to install locally. That way, if they mess up their front end, you can just give them another copy.
In runtime they will only have access to the final forms (no design/layout view , no navigation bar) so you need a switchboard and all forms will need to be accessible that way. You will need to think through the design and navigation which is a lot of extra work.
Runtime is especially effective if users don't have the full version of Access installed on their computers because any slightly knowledgeable person can change the file back to an accdb and open it in Access.
having said all that: you should also split the database and save the backend somewhere safe and just give users front ends to install locally. That way, if they mess up their front end, you can just give them another copy.
pr2-eugin
Super Moderator
- Local time
- Today, 19:39
- Joined
- Nov 30, 2011
- Messages
- 8,492
I would like to butt in here.. I would just add one more suggestion on top of what EternalMyrtle has suggested.
Create an ACCDE file, which is the Compiled version of ACCDB, so they will not be able to look at the CODE, change any design of any objects. With ACCDR, the possibility is that if the user renames the file back to ACCDB, all functionality will be back again.
So Split the Database into Front End and Back End set up. Use the Front End ACCDB -> ACCDE -> ACCDR would be the best way to go around.
Create an ACCDE file, which is the Compiled version of ACCDB, so they will not be able to look at the CODE, change any design of any objects. With ACCDR, the possibility is that if the user renames the file back to ACCDB, all functionality will be back again.
So Split the Database into Front End and Back End set up. Use the Front End ACCDB -> ACCDE -> ACCDR would be the best way to go around.
- Local time
- Today, 19:39
- Joined
- Feb 19, 2013
- Messages
- 17,813
And another thing you can do is to put a password on the back end.
You'll need to relink the front end so a knowledgeable user will know where to look to find the password but there are ways round that too.
You'll need to relink the front end so a knowledgeable user will know where to look to find the password but there are ways round that too.
Similar threads
