Re: Exceptional Error - Custom Menus deleted at startup of Access
- From: "Albert D.Kallal" <PleaseNOOOsPAMmkallal@xxxxxxx>
- Date: Fri, 26 Aug 2005 17:11:28 -0600
"Nabeel" <Nabeel@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote in message
news:8A670B41-20D7-42B1-B2DD-DEC36B433C3C@xxxxxxxxxxxxxxxx
> Yes, the machine which are generating these errors have all updates and
> patches installed for Microsoft Office 2000.
And also the updates to jet? correct?
>
> If updates would be making this kind of problems then why other machines
> are
> NOT generating this error in Microsoft Access 2000.
Hum, I don't understand the above statement at all???? I in no way hinted or
implied that installing the updates would break things. Are you now saying
that installing the updates on machines is what caused the problem? If I
read you correct, you said that some machines have the updates, and are
fine, and other machines that have the updates don't work. So, why, how, or
when would one logically make the conclusion that installing the updates
would break things? If I have compete miss-read your post, please to clearly
this to me, but I don't understand your response above at all? I did not
hint, or imply or say that installing the updates would be a source of
problems. In 99% of the cases, it is the LACK OF updates and bug fixes that
have been applied that causes problems.
I would try importing all objects into a new blank file. I would also try
testing this as a mde to see if that helps.
I would also try compiling the mdb on one of those target pc's that don't
work. Can they create a mde ok? (this will narrow down references problems).
Does the mde work ok?
So, the ONLY thing we can conclude right now is that something is different
on those problem machines, but we don't know what (do you deploy office with
user profiles via a domain sever?) . So, first, make sure all machines are
same version of ms-access (ie: same patch level), and also for JET. You
mentioned that you checked and ensured that all machines are the same
patched version for both access AND jet (very important to update JET also).
Assuming this is done, then the next thing is to check references. A quick
way is via my suggestions to try and compile the mdb to a mde ON THE
problem machine.
The above things are what I would try first. If compiling and creating a
mde works fine on the problem machine, but still does not show the menu,
then perhaps security, or restrictions on the registry are at play here.
If none of the above tests result in the mde not compiling (this would be
good!..then you can hunt down a reference problem!), then we got a difficult
problem, and I don't have a solution.
At this point, if none of the above bears any fruit, then I would look at:
Does the machine have multiple versions of access?
Does the office 2000 installer "display" when it is launched (a sure
sign that things are messed up).
Are you running some virus protection software?
--
Albert D. Kallal (Access MVP)
Edmonton, Alberta Canada
pleaseNOOSpamKallal@xxxxxxx
http://www.members.shaw.ca/AlbertKallal
.
- Follow-Ups:
- References:
- Exceptional Error - Custom Menus deleted at startup of Access !
- From: Nabeel
- Re: Exceptional Error - Custom Menus deleted at startup of Access !
- From: Albert D.Kallal
- Re: Exceptional Error - Custom Menus deleted at startup of Access
- From: Nabeel
- Exceptional Error - Custom Menus deleted at startup of Access !
- Prev by Date: RE: Disable SHIFT + ENTER
- Next by Date: Re: Disable SHIFT + ENTER
- Previous by thread: Re: Exceptional Error - Custom Menus deleted at startup of Access
- Next by thread: Re: Exceptional Error - Custom Menus deleted at startup of Access
- Index(es):
Relevant Pages
|