Need to on off design mode for forms

[QTR]

Hi

I am looking to hide or unhide through a command button that when i hit command button hide so the right click design mode must be disabled and same enabled after pressing another butoon with name enable

 

[Gasman]

Why?

 

[QTR]

Why?

Just to save user to open design mode

 

[CJ_London]

Hide or unhide what? A control? Lots of controls? A form? A report?

Look to modify the visible property- set to false to hide, true to unhide

 

[CJ_London]

Why would you want users to go into form design view?

Just disable the forms allow shortcut property. But this won’t stop a user opening a form in design view from the navigation window.

Provide the user with a .accde or rename your file as a .accdr

 

[Gasman]

Just to save user to open design mode

Supply an accde file. That is what I used to do, despite my users not being inquisitive.

 

[Pat Hartman]

they can still get into design view on an .accde, just not to code. So, also rename to .accdr. That is the absolute minimum for lockdown. @isladogs has lots more information if you need to go further on his website.

 

[Gasman]

Which is here

 

[theDBguy]

they can still get into design view on an .accde, just not to code.

Don't think they can get to Design View in an ACCDE, normally. What's the secret?

 

[Gasman]

This is what I get in an accde?

 

[Pat Hartman]

Don't think they can get to Design View in an ACCDE, normally. What's the secret?

No secret. Just open the db using the full version of Access holding down the shift key. they can't change anything compiled so no reports, forms, modules. But they can change tables, queries, and macros and do damage that way.

 

[theDBguy]

No secret. Just open the db using the full version of Access holding down the shift key. they can't change anything compiled so no reports, forms, modules. But they can change tables, queries, and macros and do damage that way.

Ah, okay, my bad. I was going by the topic of this thread, which was preventing the user from going to the design view of the Form, as the title says. So, I also mistakenly thought you were just addressing that. Sorry!

I just didn't want to miss out on any secrets, if there were any. Cheers!

 

[Mark_]

Hi

I am looking to hide or unhide through a command button that when i hit command button hide so the right click design mode must be disabled and same enabled after pressing another butoon with name enable

What are you doing to prevent the user from pressing F11 to open the navigation pane?

 

[isladogs]

No secret. Just open the db using the full version of Access holding down the shift key. they can't change anything compiled so no reports, forms, modules. But they can change tables, queries, and macros and do damage that way.

It is also possible to disable design view for tables, queries and macros in both ACCDE and ACCDB files using CommandBars.
For example, this disables design view for those objects in the nav pane:

Sub DisableNavPaneDesignView()

    With CommandBars("Navigation Pane query or macro Pop-up")
      .Controls(3).Enabled = False
    End With
   
    With CommandBars("Navigation Pane List Pop-up")
      .Controls(2).Enabled = False
    End With

End Sub

Similar code can be used to disable design view from table / query datasheets (etc). You just need to know the names and index numbers of the various command bars & their captions. Alternatively loop through all CommandBars and disable DesignView in all cases

Disable Design View in Database Objects

This article explains how you can use code to disable design view to prevent changes to the design of all database objects in ACCDB files

isladogs.co.uk

WARNING:
Unless reversed, the changes are permanent and apply to all other databases
To prevent that, make sure you re-enable the CommandBars before closing the database.

 

[arnelgp]

Unless reversed, the changes are permanent and apply to all other databases

so the code is dangerous.
if you forgot you have this code and run it on autoexec macro and totally forgotten about it, you'll have a hard time figuring out why you can't edit such objects.

 

[Gasman]

so the code is dangerous.
if you forgot you have this code and run it on autoexec macro and totally forgotten about it, you'll have a hard time figuring out why you can't edit such objects.

That would be me.