Access 2003 buttons not working in Access 2000

[steve99jones]

Hi,

I've created a database in access 2003 with the default file format being Access 2000. Everything works fine on my computer and many others, all of whom are running different versions of access (2000, 2002 & 2003).

I have not had any problems with this database until recently and in the last few weeks we have had 2 users, both of them being Access 2000 users who have had the same problem.

The problem they are having is that when they click on any of the switchboard items, the buttons depress an then come back up again when the cursor is moved away, but nothing else happens - no action, no error message - nothing!!! Its the same for all of the buttons on the switchboard.

Does anyone know what is causing this? I have another computer with Access 2000 on it and this works fine, as it does on several other computers runiing Access 2000, I just cannot understand why it is not working on these 2 particular machine.......

Many thanks in anticpation.

Steve

 

[Newman]

It looks like a references problem.
Open the VBA page and choose the «Tools» menu, then «References».
There, look for a line stating «Missing». Delete it and replace with the good version if possible.

If I am off the track, come back with more info.

 

[steve99jones]

'Missing'

Hi Newman,

Thanks for your suggestion. I have looked through all of the coding references and can not find any line detailing 'missing' I was thinking that this may be a macro problem or security as it had only effected a couple of machines with Access 2000 whereas other Access 2000 machines are running the same programmes perfectly. Searching through the internet, I have seen this problem being raised a few times on different forums but there never seems to be a reply - I really need some help on this!! - Anyone??

Many thanks

Steve

 

[Newman]

If you have not tried it before, ...
Ask a user which is able to do it to try it on the other guys' PC. Or ask these other guys to try it on a computer that used to work fine. This way we'll know if it is related to some Access security problems.
Else, I don't have any idea, yet, about what might be doing this...