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

Menu Bar corruption

P: n/a
I have a large Access application that I look after. This app is
written in Access 2000 and uses menu bars. (CommandBars and CommandBar
Controls).

The menu is static - built into the app (ie items aren't added to it or
deleted from it at runtime). The Menubar was created and forms dragged
onto it in the usual fashion.

The app is compiled into an MDE.

Problem is that I am seeing errors occur with machines with bluetooth
software, most notably the Bluetooth clients that ships with HP
laptops.

The menu bar will be there but click on any of the menus and there's
nothing there, or else a bluetooth menu.

My users are all around the world, so it's a case of support-by-email.

My usual instruction is to use Regedit to navigate to anr delete the
hive HKCU\Software\Microsoft\Office\nnn\Access\Settings \CommandBars
(where nnn is the version of Access in use).

This restores the menus for a short while, the problem always returns.

Googling this problem yields surprisingly few (zero) results.

Anyone else struck this or found a way around it??

Nov 27 '06 #1
Share this Question
Share on Google+
4 Replies


P: n/a
"Adam Rosner" <ad*********@gmail.comwrote in message
news:11**********************@j44g2000cwa.googlegr oups.com...
>I have a large Access application that I look after. This app is
written in Access 2000 and uses menu bars. (CommandBars and CommandBar
Controls).

The menu is static - built into the app (ie items aren't added to it or
deleted from it at runtime). The Menubar was created and forms dragged
onto it in the usual fashion.

The app is compiled into an MDE.

Problem is that I am seeing errors occur with machines with bluetooth
software, most notably the Bluetooth clients that ships with HP
laptops.

The menu bar will be there but click on any of the menus and there's
nothing there, or else a bluetooth menu.

My users are all around the world, so it's a case of support-by-email.

My usual instruction is to use Regedit to navigate to anr delete the
hive HKCU\Software\Microsoft\Office\nnn\Access\Settings \CommandBars
(where nnn is the version of Access in use).

This restores the menus for a short while, the problem always returns.

Googling this problem yields surprisingly few (zero) results.

Anyone else struck this or found a way around it??
I have seen EXACTLY the same thing only it was an IBM Thinkpad with bluetooth.
In my case menu items directly on the bar were okay but sub-menus had nothing
listed except "Other". If you clicked on the "Other" something to do with
Bluetooth came up.

I never found a solution. I ended up replacing the menu bar with a single
on-bar button labelled "Menu" that caused a shortcut menu display to appear.
This basically translated to a vertical menu instead of a horizontal one (which
I sort of liked better anyway).

--
Rick Brandt, Microsoft Access MVP
Email (as appropriate) to...
RBrandt at Hunter dot com

Nov 28 '06 #2

P: n/a

Rick Brandt wrote:
I have seen EXACTLY the same thing only it was an IBM Thinkpad with bluetooth.
.....
I never found a solution.
I've written a knowledgebase article for my users.
http://www.superstructuregroup.com/a...D=9&EntryID=30

Adam.

Nov 28 '06 #3

P: n/a
"Adam Rosner" <ad*********@gmail.comwrote in
news:11**********************@h54g2000cwb.googlegr oups.com:
Rick Brandt wrote:
>I have seen EXACTLY the same thing only it was an IBM Thinkpad
with bluetooth. .....
I never found a solution.

I've written a knowledgebase article for my users.
http://www.superstructuregroup.com/a...iew=entry&Cate
goryID=9&EntryID=30
Wow, what an awful problem.

Does the Bluetooth driver provide some kind of MS Office menu
add-in? If so, is it then possible to disable that in the Bluetooth
software installation or configuration routines (assuming there are
such)? Just a thought -- I've seen these kinds of things cause
enormous problems and be extremely difficult to get under control.

--
David W. Fenton http://www.dfenton.com/
usenet at dfenton dot com http://www.dfenton.com/DFA/
Nov 28 '06 #4

P: n/a

David W. Fenton wrote:
>
Wow, what an awful problem.
Yeah. I've got 4 developers working on the app to bring it into the
21st century... if we find a solution to this problem I'll put it on
that same knowledgebase article. Hopefully in time Google will pick it
up.

A

Nov 28 '06 #5

This discussion thread is closed

Replies have been disabled for this discussion.