Question Ribbon showing with RDP Connection

[txgeekgirl]

I am using the following code to turn off the Ribbon and hide the Nav Bar in an Access DB.

 'turn off ribbon
    DoCmd.ShowToolbar "Ribbon", acToolbarNo

 'turrn off nav pane
    strTableName = DLookup("Name", "mSysObjects", "[Type] = 1 AND [Flags] = 0")
    DoCmd.SelectObject acTable, strTableName, True
    DoCmd.RunCommand acCmdWindowHide

Furthermore, under File/Options I have turned off all of the options for the Ribbon and Nav.

When accessing the Database from the server side, everything works as I would want it. There is no Ribbon or Nav Bar showing at all. However, with an RDP connection, there is still a default Ribbon. Does anyone know how to turn this off?

 

[Ari]

Hi

Paste here a "print screen" to see that this is ribbon.

What is your version of Access?

 

[txgeekgirl]

I am running Access 2010

I don't think the img is going to copy - it shows File Home Add-Ins

Home has limited functionality but more than I'd like. and because the ribbon is on so is the ability to right click a form and have that functionality.

 

[Ari]

Try disabling the following path:

Access Options> Trust Center> button 'Trust Center Setting "> Add-ins> Select "disable all application add-ins ... "

 

[boblarson]

I am running Access 2010

I don't think the img is going to copy - it shows File Home Add-Ins

Home has limited functionality but more than I'd like. and because the ribbon is on so is the ability to right click a form and have that functionality.

You have to ATTACH the image here first. You can't just copy and paste. I'm surprised as I would have thought you would have known that (from being here long enough)

 

[boblarson]

and because the ribbon is on so is the ability to right click a form and have that functionality.

That does not control that functionality. You need to uncheck the ALLOW DEFAULT SHORTCUT MENUS as well.

But still, have you created your own ribbon and assigned it as the default? If not, you should. This will remove almost all functionality:

In the UsysRibbons table (if you don't have one you will need to create it).

Use this as the XML:

<customUI xmlns="[URL]http://schemas.microsoft.com/office/2006/01/customui[/URL]">
<ribbon startFromScratch="true">
</ribbon>
</customUI>

Then, if it happens to show, it won't matter.

 

[Pat Hartman]

I fought for weeks with the nav pain (sic) and ribbon and couldn't stop them from appearing when certain instructions were executed - in one case, it was TransferSpreadsheet which I used to import data. Once they appeared, there was no code that I could find that would make them go away again. The solution I ultimately discovered was if I distributed the app with an .accdr extension rather than .accde, the ribbon and nav pane would stay hidden.

 

[txgeekgirl]

You have to ATTACH the image here first. You can't just copy and paste. I'm surprised as I would have thought you would have known that (from being here long enough)

Bob - Duh - I have never attached a file. OK - I attached one.

What is the difference releasing with an accdr extension?

 

[txgeekgirl]

My concern is not just for the code but we are accessing the HR database in this particular program and managing time sheets - so there is personal info on the back tables that really even I shouldn't be privy to - but as the designer needed.

 

[Pat Hartman]

There is no way to protect sensitive data stored in a Jet/ACE database. If the data is sensitive, move it to SQL Server. Renaming the extension to .accdr is a trick. It tells Access to pretend to be the runtime engine and the runtime engine prevents access to anything but the forms the designer made available. But it is just a trick. A savvy user could rename the extension to .accde or .accdb and gain access to the tables as long as he is using the full version of Access.

 

[txgeekgirl]

Started reading about converting to .accdr - maybe not the best choice for this situation - forms will work in runtime but the reports won't.

I think I will strip the quick menu off the top and leave the ribbon - maybe try to break into the back code off the ribbon.

 

[Pat Hartman]

The .accdr extension is just a trick. It doesn't change anything. All it does is tell Access to pretend to be the runtime engine. All you need to do to get back to unprotected is rename the database extension to .accde or .accdb