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\M icrosoft\Office \nnn\Access\Set tings\CommandBa rs
(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??
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\M icrosoft\Office \nnn\Access\Set tings\CommandBa rs
(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??
Comment