Read only mode in Access 2010

[mo9rissat]

Hello,

I'm working in Access 2010. I created a database that I want to post in a server on the read-only mode, so that users can not change forms or querys. How can I do this in Access 2010?

Thank you for your help.

 

[smartascii]

If your data is added exclusively in forms, you can give your users Access 2010 Runtime, which only has the capacity to display forms and allow data entry through them. It also has the added benefit of not requiring a license (I think), which may save you some money. One caveat: because it lacks even the capacity to choose which forms to display, you'll have to set your database to open the correct form on launch, and use buttons or navigation forms to allow your users to move between forms, if you have multiple.

 

[mo9rissat]

Good morning and thank you for your answers.

Yes I tried to put my database in *. Accde mode but it allows the user to see the forms in creation mode, so they can change them.

For the *. Accdr (runtime) I tested it, it meets my needs but when I launch the database, I see a message that is a little scary:
A potential security issue has been identified....

Any solution for that messages??

 

[mo9rissat]

Hello,
Thanks for your response and your help.
For now I just converted my database to *.accdr in order to set it in the read only mode.

I think that the idea of ​​splitting the DB in FE and BE is good but I do not know how to do it.

Did you just rename the file? You need to actually create the .accde through the Access interface. The users CANNOT get into design view for forms/reports/modules once you do that. Try again. Also make sure you don't lose the .accdb because you cannot go back. If you need to make changes, you'll need to make them to the .accdb and then recreate the .accde.

I reread your initial post and it sounds like you have all the users sharing the same database. That makes for an unstable environment. You need to split the database into an FE and BE if you haven't done so already and distribute the FE to each user so they have their own personal copy on their local hard drive.

smartascii - giving users the Access runtime doesn't do anything to protect the database. They can still open it with the full version if they have it or simply copy the file and take it home to play with. Granted, the .accde doesn't give much protection but it does give some.

After creating the .accde, you can rename it to .accdr. That tells Access to pretend to be the runtime engine so the user will not under any conditions be able to get to design view on anything which on the surface is exactly what you want. However, if the user reads these forums, he will know that he can simply rename the file back to .accde and get in and mess with the queries and macros. He'll have to open the BE to mess with the tables.

 

[Ramnik]

well can we use the user authentication kind of method to secure our database >???? any suggestions about multiple users having multiple limitations ... how to achieve this kind of functionality ......thankssss

 

[quotegirl]

I'm "stuck" in read only mode. How do I get out of it. HELP!!!

 

[quotegirl]

I'm trying to make changes to the table and I cannot make changes because it states in read only mode. I know enough about Access to be dangerous...I've never had this issue before...2 years of working this product and now I'm at a loss. It states I have to save it, which I've done but still cannot make changes or get it out of read only mode. Any other suggestions?

 

[quotegirl]

I get an error that says "your microsoft office database or project contains a missing or broken reference to the file INFRARED.OCX version 1.0 it states I must fix this reference...I don't know what it is...???