DataBase - Access 2007
Asked By PremierSoftwar
27-Feb-09 04:05 AM
Hello!
Can anyone help me please ... how do I turn off Access 2007's ribbon when I
open an Access 2000 dB application?
Thanks in anticipation.
DoCmd.ShowToolbar
(1)
Access 2003
(1)
Access 2007
(1)
VBA
(1)
AllowBuiltInToolbars
(1)
AllowFullMenus
(1)
Douglas J. Steele replied...
You mean you would like to get the old menu instead of the ribbon? Sorry, you
cannot.
--
Doug Steele, Microsoft Access MVP
http://I.Am/DougSteele
(no e-mails, please!)
PremierSoftwar replied...
I just want to "turn-off" or "hide" the thing (it is taking up too much screen
space) ... is that possible?
Sky replied...
Ctrl-F1 minimizes it. Or right-click on it, then Minimize.
PremierSoftwar replied...
No ... sorry ... I am looking for code to do it ...
Sky replied...
DoCmd.ShowToolbar "Ribbon", acToolbarNo completely hides the ribbon.
But if this is for a custom application, you probably want some kind of
menus and/or toolbars. Of course, you can specify toolbars, ribbons, and
menus in your form and report properties.
You can also make Access run with your custom Access 2003-style menus and
toolbars and no ribbon, by setting the startup properties: File (Alt-F),
Access Options, Current Database, Ribbon and Toolbar Options, then turn off
Allow Full Menus and Allow Built-in Toolbars. You can set these options
programmatically the same as Access 2003 (AllowFullMenus and
AllowBuiltInToolbars), but this does not take effect until you reopen the
database.
- Steve
PremierSoftwar replied...
Thank you ... I will try these ...
Karl replied...
I tried to insert the ShowToolbar as a Macro Action for a form load and it
does not recognize Ribbon or even "Ribbon" name.
Sky replied...
I don't know anything about Macro Actions. The following VBA code works for
me, as I originally posted:
DoCmd.ShowToolbar "Ribbon", acToolbarNo
You might use VBA rather than macros, for many reasons.
- Steve
Karl replied...
Yup! It worked as you said. Rather than using a RunCommand, ShowToolbar,
Ribbon, in a Macro Action (it didn't recognize Ribbon as a toolbar), I
created a Function, named it HideRibbon(), used your code, then called it
with a RunCode, HideRibbon() in my Macro Action. Thanks for your help.

Roger Jennings on Access / Sharepoint DataBase http: / / www.quepublishing.com / articles / article.aspx?p = 1606238 I was very dismayed is it makes it pretty clear that in-house hosting of your Sharepoint server with Access Services to support browser-based Access apps is something only large companies will be able to afford, because the pricing and licensing for the Enterprise version is very, very steep. The alternative is hosted Sharepoint / Access Services, and the costs do not seem terribly high. It seems to me that the pricing is upside-down. Big enterprises do not want to deploy Access apps in the browser - - they will build their own .NET apps, browser-based or not 2010, it could vastly increase those costs for organizations with legacy hardware). The features of Access 2010 used in conjunction with Sharepoint 2010 seem to me to be most compelling for and small businesses. I do not know if I could sell clients on hosted Sharepoint / Access. I have been able to sell clients on hosted Exchange, and it is been very W. Fenton http: / / www.dfenton.com / contact via website only http: / / www.dfenton.com / DFA / Access Discussions SQL Express (1) SQL Server (1) MySQL (1) Exchange Server (1) Windows Server (1
Access 2010 for software development DataBase Hi, What do I need to use Access 2010 (or perhaps 2007) to port our 2003 application and create an executable (MDE in Access 2003)? Are there any issues with 2010? -paulw Access Discussions SQL Server (1) SharePoint (1) Albert D. Kallal (1) Office 2007 (1) Office 2003 (1) Access 2007 (1) Access 2010 (1) Access 2003 (1) You can
Access 2010 with Sharepoint 2010 DataBase I found this article http: / / sharepointproconnections.com / Articles / tabid / 149 to me was these two points: client." Hopefully this means you can test out the Access 2010 in a browser capabilities. 2.0 AA compliance. Level 1 browsers, which support 100 on other platforms. Level 2 browsers will have some limitations in rendering and behavior." Bob Access Discussions SQL Server (1) MySQL (1) Visual Basic for Applications (1) SharePoint (1) Access 2007 (1) Access 2010 (1) Office 2003 (1) Windows 7 (1) Well, the question is do you really need to go to now we build applications to the office standard (that might use outlook, excel, and MS access on the desktop), in the future we build applications that does all the similar functions
Considerations migrating from Access 97 mdb to Access 2003 (or up)? DataBase What are the things I need to watch for? I know about sheet properties and Sandboxing mode and making sure to run Jet 4.0 SP8 for 2003 but what else should I look for? We're kind of at the end of the road (so it seems) with Access 97. It does not play well with Windows 7 Professional even in XP Mode, the is crashy / unsreponsive at times. I figure moving up to a more 'modern' version of Access can help alleviate some of these problems and allow it to run native in Windows XP mode. So I am all ears for recommendations on migration or ways to get Access 97 to work properly in Win 7. Thanks a bunch. Access Discussions Visual Studio .NET (1) Windows XP (1) Office 2007 (1) Access 2007 (1) Access
Both Ends: - AllowSpecialKeys = False (prevents F11) - AllowByPassKey = False (prevents holding Shift during startup) - StartUpShowDBWindow = False - AllowBuiltInToolbars = False - AllowFullMenus = False - AllowShortcutMenus = False - AllowBreakIntoCode = False The main security hole (and my developer access) was to use an auxiliary database with VBA code that alters the frontend or backend AllowByPassKey property. Then I could open the frontend organization. This worked well with A2000. But now with A2007, the ribbon has the Quick Access Toolbar. The QAT has a small dropdown arrow on the right- side that lets the user select More Commands -> Current Database -> change the "Use Access Special Keys" property. They can also change the startup form. Then the user can close allow the use of the ribbon and / or the QAT without allowing the user to access the Current Database settings? I realize that I can use DoCmd.ShowToolbar "Ribbon", acToolbarNo But then users lose access to simple buttons like - Sort Ascending - Sort Descending