Error Message in MDE file on some PCs

[Guest]

I have an MDE file installed on a number of PCs. On some PCs, a form that
displays a Microsoft Project Gantt chart, and is used to import data from
MSP, has an error.
"The expression On Mouse Move you entered as the event property setting
produced the following error: Object or class does not support the set of
events"
This happens when the cursor moves over a button that has an event for On
Mouse Move to set the focus to the button. (me.btnImport.setfocus)
Basically Access seems to loose the plot and the only way you can get out of
the form is to move the cursor around all the buttons and close the form.
Very often, Access needs to be closed down and restarted before it will
function again.
I have not been able to identify why it happens on certain PCs. The
application is an Access 2000 application running on a mix of Access 2000 and
Access 2003 installations. I have a suspicion it is something to do with
references but have checked out the PCs and all the references are available.
I did a Google search and found reference to the problem in one forum but no
solution. Is it a known issue? Is there a way around it?

 

[Brendan Reynolds]

It certainly sounds like it might be a references problem. Unfortunately,
problems with references are difficult to track down in an MDE. Could you
take a copy of the MDB to one of those problem PCs, and build an MDE from
the MDB on that PC? (You can delete the MDB from that PC afterwards).

If you can do that, check the references in the MDB on the problem PC before
building the MDE. If any are marked as 'missing' you'll need to investigate
further. If none are marked as 'missing', try removing a reference, closing
the References dialog box, then going back and adding the reference again,
to refresh the references. Now create the MDE.

If you're lucky, you may be able to copy that MDE to the other problem PCs -
it depends on how many different versions of the referenced object libraries
there are, or in other words whether all the problem PCs have the *same*
problem or not. If you're unlucky, you may have to repeat the process on
some of the other problem PCs - unless you can get them standardised so that
they all have the same versions of the referenced object libraries.

 

[Guest]

Thanks Brendan. I will give it a try.

It certainly sounds like it might be a references problem. Unfortunately,
problems with references are difficult to track down in an MDE. Could you
take a copy of the MDB to one of those problem PCs, and build an MDE from
the MDB on that PC? (You can delete the MDB from that PC afterwards).

If you can do that, check the references in the MDB on the problem PC before
building the MDE. If any are marked as 'missing' you'll need to investigate
further. If none are marked as 'missing', try removing a reference, closing
the References dialog box, then going back and adding the reference again,
to refresh the references. Now create the MDE.

If you're lucky, you may be able to copy that MDE to the other problem PCs -
it depends on how many different versions of the referenced object libraries
there are, or in other words whether all the problem PCs have the *same*
problem or not. If you're unlucky, you may have to repeat the process on
some of the other problem PCs - unless you can get them standardised so that
they all have the same versions of the referenced object libraries.