Re: command buttons not responding

Tech-Archive recommends: Fix windows errors by optimizing your registry

You say the code doesn't do anything when you click the button after
installing SP3? Have you put a breakpoint in the code and stepped through it
to verify if it is or isn't running? If it is running but not doing what you
want, what do you have as an error handler? If you have On Error Resume Next
or just trap the error and exit, then it will simply appear as if the code
isn't running, but it really is running but getting an error.

After you open the form in design mode and go back to form view again, does
it work from that point on or does it start not working again?

Right off-hand, it sounds as if something is corrupted. For information on
working with a corrupted database, see this link.

http://www.allenbrowne.com/ser-47.html

--
Wayne Morgan
MS Access MVP


"Bren" <Bren@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote in message
news:A22D08F8-F99A-4AE9-A776-F80940492A93@xxxxxxxxxxxxxxxx
>I have a ms access database that is having an issue on only certain
>machines.
> It seems to have started once the ms office 2000 sp3 was installed. The
> database has a main form with command buttons that either open forms or
> open
> reports. The on-click property doesn't seem to respond once this patch is
> loaded. I've checked that the reference to the on-click procedure is
> still
> there, which it is. Once I open the form in design mode and switch back
> to
> form view the buttons respond just fine. I've check the dll file
> references
> and they all seem to be fine. To get around the problem, we uninstalled
> sp3
> and the buttons respond correctly. But, due to the vulverablilty, we'd
> like
> to figure out what is causing this problem. Any help is greatly
> appreciated.


.

Quantcast