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

Hide the Menu Bar from view obstacle!

P: n/a
Access2k non runtime.

In a previous post, I mentioned that I wanted to hide the Access 'Menu
Bar' from view. That means that I DO NOT want to be able to see the
MenuBar, even as a momentary flash during the load of my project!

I thought I had accomplished this using the:
CommandBars("Menu Bar").Enabled = False In conjunction with a custom
blankmenu. But, as it turns out, it removed the default menuBar from
Access itself. This is not acceptable!

By this I mean that when Access is run without an app, the MenuBar is
absent. I can Restore the MenuBar at the close of my app, but this
causes it to be seen at the ReStart of the app, and then it becomes
removed.

It seems there is no way to accomplish this. This would have given my
app a clean load appearance, without revealing any sign of MS Access
at the startup since I also eliminated the Access Banner, Icon, and
other items successfully. This remains the ONLY obstacle, and it
seems MS could have easily provided this option.

May 14 '07 #1
Share this Question
Share on Google+
3 Replies


P: n/a
On May 14, 12:24 pm, "ApexD...@gmail.com" <ApexD...@gmail.comwrote:
Access2k non runtime.

In a previous post, I mentioned that I wanted to hide the Access 'Menu
Bar' from view. That means that I DO NOT want to be able to see the
MenuBar, even as a momentary flash during the load of my project!

I thought I had accomplished this using the:
CommandBars("Menu Bar").Enabled = False In conjunction with a custom
blankmenu. But, as it turns out, it removed the default menuBar from
Access itself. This is not acceptable!

By this I mean that when Access is run without an app, the MenuBar is
absent. I can Restore the MenuBar at the close of my app, but this
causes it to be seen at the ReStart of the app, and then it becomes
removed.

It seems there is no way to accomplish this. This would have given my
app a clean load appearance, without revealing any sign of MS Access
at the startup since I also eliminated the Access Banner, Icon, and
other items successfully. This remains the ONLY obstacle, and it
seems MS could have easily provided this option.

Why not write and use a custom (empty?) menu and use that as the menu
for the form(s) and or report(s) in question?

May 14 '07 #2

P: n/a
Why not write and use a custom (empty?) menu and use that as the menu
for the form(s) and or report(s) in question?
I tried that David:
>CommandBars("Menu Bar").Enabled = False
In conjunction with a custom blankmenu.
It did not work to eliminate what I'm trying to accomplish:
I DO NOT want to be able to see the
MenuBar, even as a momentary flash during the load of my project!

May 14 '07 #3

P: n/a
Well, my solution is to use the /runtime switch on start-up, and provide a
custom menu bar...

that way, you don't get the ms-access menu bar flashing by....

You do get a windows menu bar file, edit, windows..etc. On the other hand,
for the last 16 years, virtually every application I purchased had a menu
bar...not like you going to shock anyone!!!

in fact, if you don't use the runtime switch, then you see the ms-access
icon during start-up EVEN IF you specify a custom icon for the start up.

So, if you success hide the menu bar, you will still see the ms-access icon.

I would simply provide a decent looking menu bar, and specify that for your
application. Along with the runtime switch, then they not know it
ms-access.....

further, the /runtime switch has the added bonus of disabling the shift key
by-pass.

It seems strange that you trying to get a windows like look, and then yet
forgot to add a custom menu bar that 99.9999% of all applications you
purchased have one!!!

if you looking to build something that has a commercial feel, then you need
to build with the runtime in mind. further, by proving custom menus, you
control he look and feel, and father have a "ready" made application that
can be deployed without your client need to purchase ms-access, but running
on a runtime. This means the targer mahcine will not need ms-access...

--
Albert D. Kallal (Access MVP)
Edmonton, Alberta Canada
pl*****************@msn.com
May 15 '07 #4

This discussion thread is closed

Replies have been disabled for this discussion.