Darryl Collins
Darryl.Collins at iag.com.au
Tue Dec 14 21:06:03 CST 2010
_______________________________________________________________________________________ Note: This e-mail is subject to the disclaimer contained at the bottom of this message. _______________________________________________________________________________________ Not sure if this is going to help or not. In Excel I have had the same issue. Using XL2010 you can create your own custom ribbon tabs and have those tabs as the only one(s) visible to the user. This means having to recode your existing commandbar functionality into XML code. The main downside is it will stuff up your 'backward' compatiblity. XML ribbon code won't work in earlier version where command bars will. Office 2007 is far less flexible on modding the ribbon. A good plan B would be to force A2010 only to show the addin tab so you can use your exisiting command bars. I haven't tried that in A2010, but it should be possible. That is not an option for A2007 though... Anyway... hope that is useful. cheers Darryl. -----Original Message----- From: accessd-bounces at databaseadvisors.com [mailto:accessd-bounces at databaseadvisors.com] On Behalf Of David Emerson Sent: Tuesday, 14 December 2010 6:04 PM To: Access Developers discussion and problem solving Subject: Re: [AccessD] Observations on AC 2007 (not good) I have come across the situation where I want to hide the A2007 Ribbon but still show my custom menu (Database is A2002 format). Dan's code below works well for hiding the Ribbon but as is noted below, so is my custom menu hidden. Is there any easy solution to this problem? Would using an A2010 runtime make the problem easier? Regards David Emerson Dalyn Software Ltd Wellington, New Zealand At 26/11/2010, Dan Waters wrote: >I have to say that I have not had a problem with my customers running A2007 >on an mdb file. I have not tried converting to A2007 because some of my >customers still use Access 2003. So, my recommendation is to develop the >app as an mdb, give them mdb files, and they can use A2007. > >The only issue I've come across is that the ribbon shows up when forms are >open, and I needed to prevent that because my forms don't show any toolbars >and I don't want users getting any of that functionality at run time. This >can be fixed. > >When you run startup code include this procedure in a standard module while >passing in a False value: > > Private Sub DisplayRibbon(blnDisplayRibbon As Boolean) > If SysCmd(acSysCmdAccessVer) >= 12 Then > If blnDisplayRibbon = True Then > DoCmd.ShowToolbar "Ribbon", acToolbarYes > Else > DoCmd.ShowToolbar "Ribbon", acToolbarNo > End If > End If > End Sub > >This keeps the ribbon closed when a form is opened. > >But you need the ribbon when a report is opened for printing, previewing, >closing, etc. In that case I use the following code in each report: > > Private Sub Report_Close() > Call DisplayRibbon(False) > End Sub > > Private Sub Report_Open(Cancel As Integer) > Call DisplayRibbon(True) > End Sub > >At two of my customers, some people use A2007 and some use A2003, and they >all use the same mdb files without a problem. A2007 was designed to use mdb >files with little to no difference from A2003 behavior, other than the >ribbons. > >Hope this helps someone! >Dan > >-----Original Message----- >From: accessd-bounces at databaseadvisors.com >[mailto:accessd-bounces at databaseadvisors.com] On Behalf Of Mark Simms >Sent: Wednesday, November 24, 2010 11:04 PM >To: 'Access Developers discussion and problem solving' >Subject: [AccessD] Observations on AC 2007 (not good) > >As I am furiously hacking away at AC 2007 for a client, I've spotted some >problems I have not seen documented. >Here they are: >1) I observed that when changing an ACCDB to an MDB for purposes of using >Access 2003 and Access 2007 there a bug in this conversion process ...it >removes the USysRibbons table. Access 2007 still can operate without one. >However, without that system table, you cannot do any customization of the >ribbon by assignment from the Ribbon and Toolbar options setting ! The only >alternative is the LoadCustomUI vba method. >The fix: cut-and-paste the USysRibbons from an ACCDB file; then change the >Attribute to the proper system table attribute -2....... something. That >last step is important. > >2) Commandbar menu items built in AC 2003 show-up ONLY under the "Add-ins" >tab of AC 2007. OF COURSE THIS STINKS HUGELY. If you assign a custom Ribbon >that does not have an Add-ins tab, YOUR COMMANDBAR MENU IS LOST....your >users cannot do anything ! >Microsoft easily could have provided a database-level setting for the >flexible placement of the commandbar menu onto the Ribbon. How this major >oversight ever got past beta testing only confirms my feeling about the >political nature of the selection of the beta test team. I would go so far >as to indict the product manager of Access for such a grevious oversight and >lack of attention to detail. > >3) The AC 2007 ribbon can be minimized and indeed that setting "persists" >upon the next database open. Minimizing it via the GUI is simple. Doing it >with VBA is nearly rocket science with a ton of Win API calls required for >it to be reliable. Note: in AC 2010, a new DoCmd was added to minimize the >ribbon. (it took 3 YEARS to figure that out ?) > >It doesn't take a genius to see why AC usage and acceptance in corporations >has now dropped to very low levels. Anyone associated with the beta testing >of AC 2007 should immediately disavow all knowledge of any interaction with >Microsoft Access engineers and managers involved in that program at the risk >of major verbal abuse by beleagered colleagues. -- AccessD mailing list AccessD at databaseadvisors.com http://databaseadvisors.com/mailman/listinfo/accessd Website: http://www.databaseadvisors.com _______________________________________________________________________________________ The information transmitted in this message and its attachments (if any) is intended only for the person or entity to which it is addressed. The message may contain confidential and/or privileged material. Any review, retransmission, dissemination or other use of, or taking of any action in reliance upon this information, by persons or entities other than the intended recipient is prohibited. If you have received this in error, please contact the sender and delete this e-mail and associated material from any computer. The intended recipient of this e-mail may only use, reproduce, disclose or distribute the information contained in this e-mail and any attached files, with the permission of the sender. This message has been scanned for viruses. _______________________________________________________________________________________