Kaup, Chester
Chester_Kaup at kindermorgan.com
Tue Jan 13 08:41:22 CST 2009
See below -----Original Message----- From: accessd-bounces at databaseadvisors.com [mailto:accessd-bounces at databaseadvisors.com] On Behalf Of Arthur Fuller Sent: Tuesday, January 13, 2009 7:37 AM To: Access Developers discussion and problem solving Subject: Re: [AccessD] Toolbar Control Thanks, Chester. While we're on the subject, I vaguely recall that there is something special one must do in order to install a custom toolbar on a client's machine. Is that correct, or is it simply part of the MDB FE and automatically included? As I recall no further action is required. Another question, regarding your mention of Tools/References. Suppose I'm developing in A2K7 and the client will run it in A2K3. Will the specific reference to the Office library version break it? If so, is there a way to virtualize this reference, or does the developer simply tell the client how to get to Tools/References and delete the MISSING reference and then recompile, or...? Never had to deal with this so cannot help you with this question One final question. The documentation I read this morning on MSDN refers to both command bars and toolbars. Is there a difference, and if so, what is it? The names are interchangeable. Thanks, Arthur On Tue, Jan 13, 2009 at 8:22 AM, Kaup, Chester < Chester_Kaup at kindermorgan.com> wrote: > Try this > > For Each cmdBar In CommandBars > If cmdBar.Visible Then > sTemp = cmdBar.Name > DoCmd.ShowToolbar sTemp, acToolbarNo > End If > Next > DoCmd.showtoolbar "My Menu", acToolbarYes > > Make sure you have the Microsoft Office 10.0 object library declared as a > reference in Tools/References. > -- AccessD mailing list AccessD at databaseadvisors.com http://databaseadvisors.com/mailman/listinfo/accessd Website: http://www.databaseadvisors.com