Oh yes it was. It may not be visible, but it's in there. Where else
would it be?
Now if you created a new database and copied only some objects over,
the menu may not be there. But you would be more careful than that,
right?
-Tom.
>How do I associate a custom menu with a specific .MDB file?
>
[quoted text clipped - 5 lines]
>with the .MDB file I copied. I would like to keep it with the existing
>toolbar, and not rebuild everything on the toolbar.
Can Of Worms - 23 Jan 2008 14:16 GMT
From my understanding, when you open an Access database, you actually have 2
files open.... MSACCESS.EXE and the <filename>.MDB.
Wha tI had done was techincally just modify the existing toolbar (as per
Rick Brandt), which is specific to the MSACCESS.EXE file, not the .MDB. So
when I distributed the .MDB, the toolbar did not go with it, and was not
visible on other user's machines, since they were using their own
MSACCESS.EXE file.
Rick suggested the correct solution, moving it to it's own, and new,
toolbar, which is then specific to the .MDB file, and it was distributed
successfully.
-CoW
> Oh yes it was. It may not be visible, but it's in there. Where else
> would it be?
[quoted text clipped - 13 lines]
> >with the .MDB file I copied. I would like to keep it with the existing
> >toolbar, and not rebuild everything on the toolbar.
> How do I associate a custom menu with a specific .MDB file?
>
[quoted text clipped - 5 lines]
> with the .MDB file I copied. I would like to keep it with the existing
> toolbar, and not rebuild everything on the toolbar.
Did you really "create" a menu bar or modify an existing one? Modifications to
built in menus are specific to the installation of Access. They appear only on
the machine where the mods were done and all MDB files opened on that machine
will see the modifications.
Totally NEW menus are stored in the MDB file, will show up on any PC that opens
that file, and will not be seen in any other MDB file unless they are imported
into them.

Signature
Rick Brandt, Microsoft Access MVP
Email (as appropriate) to...
RBrandt at Hunter dot com
Can Of Worms - 23 Jan 2008 14:07 GMT
> > How do I associate a custom menu with a specific .MDB file?
> >
[quoted text clipped - 14 lines]
> that file, and will not be seen in any other MDB file unless they are imported
> into them.
Thank you. Although the menu I created was new, I did place it on the
original toolbar, so this probably counts as a 'modifying an existing'
toolbar.
I moved it to it's own toolbar and this corrected the issue.
-CoW
Tom van Stiphout - 23 Jan 2008 14:10 GMT
I didn't know that first part. Where are such modifications to
built-in menus stored? Presumably in the registry? If so they could
potentially be shipped with the app?
-Tom.
>> How do I associate a custom menu with a specific .MDB file?
>>
[quoted text clipped - 14 lines]
>that file, and will not be seen in any other MDB file unless they are imported
>into them.
Rick Brandt - 24 Jan 2008 01:54 GMT
> I didn't know that first part. Where are such modifications to
> built-in menus stored? Presumably in the registry? If so they could
> potentially be shipped with the app?
Slightly different per version, but on my PC with Access 97...
[HKEY_CURRENT_USER\Software\Microsoft\Office\8.0\Access\Settings\CommandBars]
This not only contains mods, but also docking, position, show/hide, etc..
Deleting everything in that registry folder is the same as resetting all menus
and toolbars to their original default configuration.
I suppose you could copy those registry entries onto another machine, but since
they are Access wide, rather than file specific it would be a bit presumptuous.
Sort of like changing their screen resolution to suit one Access app.

Signature
Rick Brandt, Microsoft Access MVP
Email (as appropriate) to...
RBrandt at Hunter dot com
Tom van Stiphout - 24 Jan 2008 03:05 GMT
Thanks. I agree, better to have a custom menu bar, which you
suggested and the OP implemented.
I love the ribbon for A2007. I'm already looking forward to an even
more powerful rendition of that in the next version.
-Tom.
>> I didn't know that first part. Where are such modifications to
>> built-in menus stored? Presumably in the registry? If so they could
[quoted text clipped - 11 lines]
>they are Access wide, rather than file specific it would be a bit presumptuous.
>Sort of like changing their screen resolution to suit one Access app.