Using Access 2010. I am using a custom ribbon with startfromscratch=true. My
custom tabs/buttons appear and work. However when a form is open in
datasheet view, the contextual datasheet tab suddenly appears. This tab
contains the button to switch to design view - something users should not
have access to. I have found info on creating one's own contextual tab, but
nothing on disabling the built-in one. How can this be disabled?

--

AG
Email: npATadhdataDOTcom

One of a form's properties to restrict views available; how about setting
"allow datasheet view" to NO?

You should also consider making your front end an MDE, so no design view or
code access is possible.


"agiamb" <NOSPAMagiamb (AT) newsgroup (DOT) nospam> wrote

Thanks for the reply Ed.
Some of the forms are datasheets, so turning that off is not an option.

As for making the FE an accde, I am the subcontractor and the spec is an
accdb.

--

AG
Email: npATadhdataDOTcom


"Ed Robichaud" <edrobichaud (AT) wdn (DOT) com> wrote

"agiamb" wrote in message news:itdtv1$mga$1 (AT) dont-email (DOT) me...

--

Bring up the form in design mode, in the property sheet "other" tab for the
form, you can set the shortcut menu = no
(this option exists for most versions of access, as least going back to
2000, if not sooner).

Another possible consideration is to un-check the short cut menu option in
file->options->current database

In the Ribbon and tool bars section, you find the option

[x] Allow default shortcut menus

And, again, the above is a long time option we had in Access.

So, you have a choice here. I should point out that the right click filter
options that now appear in 2007/2010 are rather amazing.


--
Albert D. Kallal (Access MVP)
Edmonton, Alberta Canada
Pleasenospam_kallal (AT) msn (DOT) com

Thanks for the reply Albert,

I do agree that the new filtering options are good, except for the fact that
they took out the ability to use multiple criteria and operators (like
and/or) for a field.

My current problem is not with the filter/sort options, but with the fact
that the contextual tab gives users access to design view. What's with that?
Shouldn't it be our decision as to whether or not users have design access?

I do have 'Allow default shortcut menus' turned off, but that does not
affect the contextual tabs.
I don't know if turning off shortcut menus on the form level would affect
it, but that is not an option since there are custom shortcut menus in use.

I have tried setting allow full menus to false and other things I don't even
remember, but can't find anything that affects contextual tabs.
Even tried creating my own to see if it would override the default, but it
just becomes another contextual tab.


--

AG
Email: npATadhdataDOTcom


"Albert D. Kallal" <PleaseNOOOsPAMmkallal (AT) msn (DOT) com> wrote

"agiamb" wrote in message news:itdtv1$mga$1 (AT) dont-email (DOT) me...

--

Bring up the form in design mode, in the property sheet "other" tab for the
form, you can set the shortcut menu = no
(this option exists for most versions of access, as least going back to
2000, if not sooner).

Another possible consideration is to un-check the short cut menu option in
file->options->current database

In the Ribbon and tool bars section, you find the option

[x] Allow default shortcut menus

And, again, the above is a long time option we had in Access.

So, you have a choice here. I should point out that the right click filter
options that now appear in 2007/2010 are rather amazing.


--
Albert D. Kallal (Access MVP)
Edmonton, Alberta Canada
Pleasenospam_kallal (AT) msn (DOT) com

On 6/19/2011 8:54 AM, agiamb wrote:
and assign this ribbon in the startup properties, you will not get those
contextual tabs.

You can still use the built-in right-click menus on your forms if you
like, although you may want to disable the design view buttons in your
start-up code.

Steve

Thanks for the reply Steve, but as I mentioned in my original post I am
already using startfromscratch=true.
Only my custom tabs are shown, except for the contextual tab, which I can't
seem to turn off.

--

AG
Email: npATadhdataDOTcom


"Sky" <Sky (AT) NoSpam (DOT) com> wrote

In case anyone is interested, this has been answered

http://social.msdn.microsoft.com/For...-5cddbb6284c2/

--

AG
Email: npATadhdataDOTcom


"agiamb" <NOSPAMagiamb (AT) newsgroup (DOT) nospam> wrote

On 6/19/2011 5:35 PM, agiamb wrote:
I checked my ribbon XML, and I do have the following:

<contextualTabs>
<!-- suppress contextual design tabs -->
<tabSet idMso="TabSetTableToolsDatasheet" getVisible="DebugOnly"/>
<tabSet idMso="TabSetTableToolsDesign" getVisible="DebugOnly"/>
<tabSet idMso="TabSetRelationshipTools" getVisible="DebugOnly"/>
<tabSet idMso="TabSetQueryTools" getVisible="DebugOnly"/>
<tabSet idMso="TabSetFormTools" getVisible="DebugOnly"/>
<tabSet idMso="TabSetFormToolsLayout" getVisible="DebugOnly"/>
<tabSet idMso="TabSetReportTools" getVisible="DebugOnly"/>
<tabSet idMso="TabSetReportToolsLayout" getVisible="DebugOnly"/>
<tabSet idMso="TabSetMacroTools" getVisible="DebugOnly"/>
<!-- permit pivot contextual tabs -->
<tabSet idMso="TabSetPivotTableAccess" visible="true"/>
<tabSet idMso="TabSetPivotChartAccess" visible="true"/>
</contextualTabs>

The DebugOnly function is a callback that enables visibility for
developer use, but disables it for release:

' callback for getVisible that is True only when debug is True
Sub DebugOnly(control As IRibbonControl, ByRef isVisible)
isVisible = false ' put your criteria for a developer version
End Sub

Steve