By using this site, you agree to our updated Privacy Policy and our Terms of Use. Manage your Cookies Settings.
444,124 Members | 1,945 Online
Bytes IT Community
+ Ask a Question
Need help? Post your question and get tips & solutions from a community of 444,124 IT Pros & Developers. It's quick & easy.

Can I transport a custom menu bar with a db file

P: 6
Hey all,
I want to burn an access database to a disc, and give it to someone else. Is there anything i need to do to ensure that the custom menu bar I created for the startup form goes with it,? like in startup options, form properties etc. I cant find anything like in Word or Excel that gives an option to store it either in the file or globally.
Ive left all boxes checked in the startup options except 'show database window', and 'display status bar'. My custom menu bar name has been selected as the startup menu bar. Ive also selected it in the properties box for all forms and reports.
If theres anything else I should do, could someone please let me know? or does access attatch it automatically?
Cheers!
Dec 10 '06 #1
Share this Question
Share on Google+
7 Replies


missinglinq
Expert 2.5K+
P: 3,532
Access DBs are pretty much self-contained. Everything in the Db will go with the .mdb or .mde file.
Dec 10 '06 #2

NeoPa
Expert Mod 15k+
P: 31,616
Try it out before burning the CD.
I think a toolbar is outside of any database and is associated with your Access Install.

You could consider adding some code to your database to add the toolbar programmatically OnOpen and delete it OnClose.
I do that in Excel but I've no code specifically for Access. Sorry.
Dec 10 '06 #3

missinglinq
Expert 2.5K+
P: 3,532
Custom toolbars, etc do travel with the .MDB files! When yu think about it, wouldn't make any sense otherwise! Why allow you to develope custom toolbars, menus, etc if you can't place them on a client's machine?
Dec 10 '06 #4

NeoPa
Expert Mod 15k+
P: 31,616
Custom toolbars, etc do travel with the .MDB files! When yu think about it, wouldn't make any sense otherwise! Why allow you to develope custom toolbars, menus, etc if you can't place them on a client's machine?
Sorry to imply you may have been wrong MissingLinq. That wasn't the idea I was after.
I was only going from my experience with Excel where the reverse is actually true (Don't ask me to explain or double-guess MS's development ideas).
If you say it works that way in Access though, that's good enough for me.
Dec 10 '06 #5

missinglinq
Expert 2.5K+
P: 3,532
Isn't that the truth. My answer was based on a AC2000 app moved to a machine running AC2003. Of course, as we all know, funny things happen from version to version, which is my biggest gripe with Billy Bob's boys in Redmond.
Dec 10 '06 #6

P: 2
Custom toolbars, etc do travel with the .MDB files! When yu think about it, wouldn't make any sense otherwise! Why allow you to develope custom toolbars, menus, etc if you can't place them on a client's machine?
Unfortunately they dont seem to - they seem to be installation dependent, ie: if you change in one db it affects all databases you open

If anyone knows a way doing this without adding code to every onload/onclose,it would be appreciated
Nov 30 '07 #7

Expert 100+
P: 446
I endorse MissingLing's guidance. The custom menu bars DO move with the app. (The tricky bit is learning how to import them from one app to the next!)

I presume you have created new menu bars and given them a new name and not just customised the default ones (sorry to ask silly questions but sometimes. . . .)

Also make sure you are not confusing Menu bars with cutom Tool bars.

Defining the preferred menu bar in start-up and calling it in each form does it for me.

You normally get an error if you try and open a form which has a named menu that is not present (can not be found)
Nov 30 '07 #8

Post your reply

Sign in to post your reply or Sign up for a free account.