Can't Open database in RunTime Mode

[quicova]

Hi Everyone.

I finished my database project and now I what to test it out in runtime before sending it to all users.

I can't figure out how to open the database as runtime. I already installed runtime but can't find it anywhere in my computer.
If I right click on the database file, there isn't any open with runtime option.

Also some users have full access and some don't. Is runtime the best way to distribute the database? I don't want anyone changing the design or the code!

Should I put some code on the AutoExec macro to star as runtime?
or even better I have a user log in form that opens on start up, is there a way to change between full access and runtime depending on the user?



Thanks so much for all your help

[ItsMe]

Whether or not RT or a full version of Access is used to open an accdb file is determined by the OS. Offering RT in an install pack is a method to insure your application will run on PC's that do not have a full version of Access installed.

If a user has Access installed on their PC, the full version of Access will open the file. It is up to the developer to ensure users do not have access to VBA modules, tables, and such.

[quicova]

Hi,

Thats great.
can you point me where I can get information on how to do that?
I seen the save & publish option and make ACCDE, but I get an error. I think is because I have link tables.

[quicova]

Ok I've seen that in the file option mode
in the current database I can turn off a lot of stuff, change the ribbon, turn of the navigation bar, etc.

However if someone right-clicks on the form the design-view mode is still available
and the file options is also available and one can turn on everything I turned off

if there a way to lock access to this options?

[ItsMe]

I explain some of the nuances in this link, post #5

https://www.accessforums.net/queries...ons-38695.html


I take it to the extreme ans use DoCmd.ShowToolbar "Ribbon", acToolbarNo

This is the best way I have found to hide the backstage and prevent users from leaving the program, short of unplugging the computer or closing the app. However, hiding the ribbon makes it necessary to offer special controls for the user to navigate, print, search, etc.

If you need to prevent users from malicously going into the program you can move to accde. Otherwise, hiding the nav pane, toolbars, etc. should suffice. Just be sure to build in a way for you to bypass these things from happening when you need to edit.