You can use your favorite social network to register or link an existing account:
Or use your email address to register without a social network:
Sign in with these social networks:
Or enter your username and password
Forgot your password?
Yes, please link my existing account with for quick, secure access.
No, I would like to create a new account with my profile information.
This is the third post in my short three-part series on ribbon customizations in Access. In the previous post, I showed how you could fill a dropdown with a list of the open forms in the database. This time, we'll fill a dynamicMenu control in a ribbon customization with a list of open objects of any type. This might be useful to let users switch between open objects in an application.
Again, we'll start with the XML for customization:
<customUI xmlns="http://schemas.microsoft.com/office/2006/01/customui"> <ribbon startFromScratch="false"> <tabs> <tab id="tab1" label="Object Helpers"> <group id="grp1" label="Helpers"> <dynamicMenu id="dynObjectList" label="Open Objects" getContent="OnGetObjectList" invalidateContentOnDrop="true" size="large" imageMso="EditListItems"/> </group> </tab> </tabs> </ribbon></customUI>
Add this customization as a record in a USysRibbons table and set the RibbonName property of the database to match the entry in the USysRibbons table.
Before I go into the details of the callbacks, there are a few things you should keep in mind about the dynamicMenu control:
The dynamicMenu control also has this pretty cool attribute called invalidateContentOnDrop. When set to true, this causes the control to invalidate which means that the getContent callback is executed for the control. This allows you to show the most recent information in the menu. Given that, let's add the VBA for the callback. Remember that you'll need a reference to the Microsoft Office 12.0 Object Library to compile this code.
' build the list of open objectsPublic Sub OnGetObjectList(ctl As IRibbonControl, ByRef content) ' add menu content = "<menu xmlns=""http://schemas.microsoft.com/office/2006/01/customui"">" ' tables content = content & BuildOpenObjectList(acTable, CurrentData.AllTables) ' queries content = content & BuildOpenObjectList(acQuery, CurrentData.AllQueries) ' forms content = content & BuildOpenObjectList(acForm, CurrentProject.AllForms) ' reports content = content & BuildOpenObjectList(acReport, CurrentProject.AllReports) ' macros content = content & BuildOpenObjectList(acMacro, CurrentProject.AllMacros) ' modules content = content & BuildOpenObjectList(acModule, CurrentProject.AllModules) ' close the menu content = content & "</menu>"End Sub
You'll notice that this routine calls a helper function called BuildOpenObjectList which is used to create the necessary XML for a menu at runtime. Here's the helper function.
Private Function BuildOpenObjectList(lngType As AcObjectType, col As AllObjects) As String Dim strTemp As String Dim obj As AccessObject ' menu separator node strTemp = "<menuSeparator id=""ms|1"" title=""|1""/>" ' add the text in the menu separator Select Case lngType Case AcObjectType.acForm strTemp = Replace(strTemp, "|1", "Forms") Case AcObjectType.acMacro strTemp = Replace(strTemp, "|1", "Macros") Case AcObjectType.acModule strTemp = Replace(strTemp, "|1", "Modules") Case AcObjectType.acQuery strTemp = Replace(strTemp, "|1", "Queries") Case AcObjectType.acReport strTemp = Replace(strTemp, "|1", "Reports") Case AcObjectType.acTable strTemp = Replace(strTemp, "|1", "Tables") End Select ' add buttons for the open objects For Each obj In col If (obj.IsLoaded) Then strTemp = strTemp & _ "<button " & _ BuildAttribute("id", "btn" & CleanObjectName(obj.Name)) & " " & _ BuildAttribute("label", obj.Name) & " " & _ BuildAttribute("tag", obj.Name & "|" & obj.Type) & " " & _ BuildAttribute("onAction", "OnOpenObject") & "/>" End If Next ' return BuildOpenObjectList = strTempEnd Function
Yeah, there's another helper function in there. This one is called BuildAttribute and is used to wrap a string in quotes.
Private Function BuildAttribute(strName As String, strValue As String) As String BuildAttribute = strName & "=" & Chr(34) & strValue & Chr(34)End Function
And, lastly, there's one more helper function to replace some characters that are valid in Access object names but not very XML friendly.
Private Function CleanObjectName(ByVal strName As String) As String ' clean the object name so it is more XML-friendly Const REPLACE_CHARS As String = " <>\/{}" Dim intCounter As Integer For intCounter = 1 To Len(REPLACE_CHARS) strName = Replace(strName, Mid(REPLACE_CHARS, intCounter, 1), "") Next ' return CleanObjectName = strNameEnd Function
When you put this all together and open some objects for testing, you should have something that looks like this:
Comments: (3) Collapse
Robcooper, Sorry for posting out-of-subject, but I am unable to get a reply anywhere else :/ I have made an application using Access 2007. When running the application using 2007 Runtime on a machine which has Office 2003 installed, a potentially BIG problem occurs. The 2007 application runs fine. The problem arises when I start an Office 2003 program afterwards. During startup, the program will go through a 2-minute configuration screen, and it also prompts the user for the Office 2003 CD-ROM. This happens every time I have been running the Access 2007 Runtime application, and then starts Office 2003. How can this be avoided? I've seen a post somewhere else on the internet about a change in a registry key, but I don't want to change the registry unless I absolutely have to. I feel that Access 2007 is next to useless as a platform for retail products, as long as this issue resides. My application is ready for sale, but I dare not do it yet because of this. Most companies are still running Office 2003 or older. Looking forward to your meaningful reply!
Anders,
This is a known issue that we expect to fix in SP 1. There still is a configuration screen but it works much faster now. I don't have the official release date for SP 1 but you can read in the press about a evaluations that have been sent to TAP customers (e.g. www.crn.com/.../201800618). Clint
Clint, Thank you for your reply! Do you know if the config screen in sp1 requires the Office CD to be inserted? I can imagine my customers annoyance if they have to search for their Office CD every time they've been using my application. Anders
Comments: (loading) Collapse