|
|
I've developed a large Access application over 8 years beginning with Access
97 that relies heavily on custom context menus. It is deployed to roughly 20
users.
After converting it to Access 2002, users started to experience a custom
popup menu self-deleting under both Access 2002 retail and runtime with
service packs 1 through 3 on different PCs all with WinXP Pro. The command
bar is suddenly no longer part of the CommandBars collection and there is no
way to recover it. Users have to re-install a fresh copy of the application.
It's a random thing and therefore very hard to test but I was able to step
through code in one instance to diagnose the issue. It happens roughly 3
times per week.
Has anyone experienced this issue? How are custom CommandBars stored? What
could cause one to disappear?
I am thinking of recommending we deploy the Access 2003 runtime but am
concerned that this bug is still present.
Patrick
=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=
Patrick Jackman
Microsoft Access Developer since 1994
Vancouver, BC
604-874-5774
|
|
I not seen, or heard of this issue. So, it not a common or know problem.
I hidden all the menu bars for years and not every had problem. I do notice
that some companies that have installed the adobe pdf maker tools does cause
a extra menu bar to appear..and I have seen that..but, it not interfered at
all with my application.
Also, note that I do not use ANY code to hide the menubars, but just use the
tools->startup.
Are you using code, or simply using the tools->startup? to hide the built in
menu bars?
And, further, are you customizing the built in bars in anyway? It very
possible that group policies and registry settings on those machine prevents
changes from correctly occurring.
--
Albert D. Kallal (Access MVP)
Edmonton, Alberta Canada
pleaseNOOSpamKallal[ at ]msn.com
|
|
I am refering to custom popup menus, the kind that appear when you
right-click on a form. I create them by clicking Customize on the Tools menu
rather than by creating them with code on the fly. I do manipulate them with
code though, enabling and disabling CommandBar.Controls as required by my
application.
As I mentioned, there was no issue with any of these operations in Access
97. They only appeared with the conversion to Access 2002.
Patrick.
|
|
ok..that sounds ok to me....
Is any of the database multi-user, and if so...are they split?
--
Albert D. Kallal (Access MVP)
Edmonton, Alberta Canada
pleaseNOOSpamKallal[ at ]msn.com
|
|
Yes and yes.
"Albert D. Kallal" <PleaseNOOOsPAMmkallal[ at ]msn.com> wrote in message
news:ead9TEhuHHA.3688[ at ]TK2MSFTNGP03.phx.gbl...
ok..that sounds ok to me....
Is any of the database multi-user, and if so...are they split?
--
Albert D. Kallal (Access MVP)
Edmonton, Alberta Canada
pleaseNOOSpamKallal[ at ]msn.com
|
|
|