penfold1992
Registered User.
- Local time
- Today, 03:53
- Joined
- Nov 22, 2012
- Messages
- 169
So... I am again left to look with the issue of:
"The expression MouseMove you entered as the event property setting produced the following error: There was an error loading an ActiveX control on one of your forms or reports"
I have an active X control on my program (a loading bar sort of thing) however there is no event for "MouseMove" at all in the coding yet I am able to say that this is only happening on one version of the database. The other (previous) versions do not have the same issue even though they have the active X loading bar too.
the code contains some information that I dont wish to post on the internet however I am aware that it may be needed to find a solution.
If anyone thinks they may have an idea, I could send you the code to look at . I am in doubt as to if it has anything to do with the access 2007 common problem as I would expect it to bve the same with all the other access databases that I try to replicate the error on. I am not sure how I can describe how ekse it causes that issue though.
I hope It isnt something I have done to the database to cause this issue but I am willing to try things to not get this error message from reoccuring.
EDIT: previous versions also have the same issues however the database backed up on my PC does not. The ones on the servers do however.
"The expression MouseMove you entered as the event property setting produced the following error: There was an error loading an ActiveX control on one of your forms or reports"
I have an active X control on my program (a loading bar sort of thing) however there is no event for "MouseMove" at all in the coding yet I am able to say that this is only happening on one version of the database. The other (previous) versions do not have the same issue even though they have the active X loading bar too.
the code contains some information that I dont wish to post on the internet however I am aware that it may be needed to find a solution.
If anyone thinks they may have an idea, I could send you the code to look at . I am in doubt as to if it has anything to do with the access 2007 common problem as I would expect it to bve the same with all the other access databases that I try to replicate the error on. I am not sure how I can describe how ekse it causes that issue though.
I hope It isnt something I have done to the database to cause this issue but I am willing to try things to not get this error message from reoccuring.
EDIT: previous versions also have the same issues however the database backed up on my PC does not. The ones on the servers do however.
Last edited:
