P
Petr Dane¹
In an Access 2003 database, I have a fairly complicated form to which I
recently added a bunch of multi-level right-click menus. Fifteen, to be
exact, all from various comboboxes or textboxes. The data base suddenly
takes quite a long time to load. The form containing all these controls
still starts up reasonably, once Access is running, just the database itself
takes forever. It's not that large, barely over 30MB when repaired and
compressed.
I tried unhooking the RC menus from the controls - no improvement.
I then changed all the RC menus back to toolbars, which caused Access to
lock up for about ten minutes, with pretty high (55%) processor utilization.
Eventually, it came around, but still no improvement.
The next move was to turn off display of the newly visible toolbars, again
no help.
I finally actually removed the toolbars altogether, which again caused
Access to lock up for about ten minutes. It finally recovered and the load
time is now better, although it still seems somewhat pokey compared to how
it was before I started all this. I run it on several different machines
with varying capabilities, though, and this is just a subjective impression,
maybe not all that accurate.
Granted, some of these menus are pretty extensive, one in particular has
over a thousand options, down to three sub-levels.
Is this normal behavior? Getz, Litwin and Gilbert note that the CommandBar
object is not especially fast, but should the mere -presence- of these
objects have such a drastic effect on Access in general? The RC menus work
quite rapidly when they're being used - no noticeable delay before
displaying when right-clicking a control containing these menus, and the
code they call responds immediately.
Petr
recently added a bunch of multi-level right-click menus. Fifteen, to be
exact, all from various comboboxes or textboxes. The data base suddenly
takes quite a long time to load. The form containing all these controls
still starts up reasonably, once Access is running, just the database itself
takes forever. It's not that large, barely over 30MB when repaired and
compressed.
I tried unhooking the RC menus from the controls - no improvement.
I then changed all the RC menus back to toolbars, which caused Access to
lock up for about ten minutes, with pretty high (55%) processor utilization.
Eventually, it came around, but still no improvement.
The next move was to turn off display of the newly visible toolbars, again
no help.
I finally actually removed the toolbars altogether, which again caused
Access to lock up for about ten minutes. It finally recovered and the load
time is now better, although it still seems somewhat pokey compared to how
it was before I started all this. I run it on several different machines
with varying capabilities, though, and this is just a subjective impression,
maybe not all that accurate.
Granted, some of these menus are pretty extensive, one in particular has
over a thousand options, down to three sub-levels.
Is this normal behavior? Getz, Litwin and Gilbert note that the CommandBar
object is not especially fast, but should the mere -presence- of these
objects have such a drastic effect on Access in general? The RC menus work
quite rapidly when they're being used - no noticeable delay before
displaying when right-clicking a control containing these menus, and the
code they call responds immediately.
Petr