opening a database for use

[merlin777]

This is going to sound really thick but my minds gone blank so i'm going to ask it anyway.

How do you save the database you are working on so when the file is opened the db opens for use instead of development? Currently the filenames are .accdb and clicking on them opens in development with toolbars etc. What am I forgetting?

[JamesDeckert]

if you want it to open in runtime mode you need to append the /runtime command line option, or I think you rename the extension to .accdr

[June7]

I have never used accde or accdr.

I hide navigation pane, disable ribbon, disable function keys, disable right click menu - with db Option settings and disable File tab and X close with customization code. https://www.accessforums.net/access/...ers-48543.html

Be aware that holding down shift key when opening will bypass these options.

[Perceptus]

There are options when you click the Office button top right of access, and choose access options. You can set the startup object for the database under the "Current Database" section.

you can always employ the bypass shift key function to remove the shift bypass.

[merlin777]

There are options when you click the Office button top right of access, and choose access options. You can set the startup object for the database under the "Current Database" section.

you can always employ the bypass shift key function to remove the shift bypass.

I looked there under access options/current database but I can't see a startup object option?

[Perceptus]

There is a "Display Form" which will load a certain form on load.

or

You can create a macro that fires off a module of vba code and such. name that macro autoexec.

[merlin777]

if you want it to open in runtime mode you need to append the /runtime command line option, or I think you rename the extension to .accdr

I tried renaming to .accdr but when i click on the file icon access opens then immediately closes again.

[JamesDeckert]

Merlin,
try running updates for Office. There was an update that had to do with the runtime for Office13.