event property setting error!

[Guest]

Hello
I have created a simple database for the employees in my company, and i have
just had to change computers. I now have to work from another different PC
but when I try using the database, I keep getting error messages. They are
saying things like, "The expression ImageChanged 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." or the same message but
instead of 'ImageChanged' it says 'MouseMove'.
I just do not undersand what it is refering to or how I can go about fixing
the problem.

Any help would be much appreciated.
Thank you
Kind Regards
Rigby

 

[Allen Browne]

Sounds like a problem with references.

Press Ctrl+G to open the Immediate Window.
Choose References on the Tools menu.
Are any of the checked libraries marked with the word, "MISSING"?
If so, see:
http://allenbrowne.com/ser-38.html

If the references are okay, still in the Immediate Window, choose Compile
from the Debug menu. If it highlights an error, fix the error and repeat
until it compiles.

If you are still stuck, it might be a corruption in the database.
What version of Access are you using?
Is this the same version as your previous machine?
Does anyone else have the database open at the same time?

 

[Jeff]

I am getting same error in a project of mine
I tried Allen's suggestions - still have error

If you find solution please let me know.
Jeff @ Bennet-Tec.com
If you send me msg with your e-mail I'll be happy to do the same
I'll try to also post back here if I can find this thread again


* * Please include a copy of this message with your reply

Jeff Bennett
(e-mail address removed)

* Bennet-Tec Information Systems, Inc
* 50 Jericho Tpk, Jericho, NY 11753
* Phone 516 997 5596, Fax - 5597
* RELIABLE Components Make You Look Sharp!
* TList/Pro * ALLText HT/Pro * MetaDraw *
* Custom Software Development Services Too.
* WWW.Bennet-Tec.Com

=================== ===================

 

[Guest]

Dear Allen

Thank you for your advice. Unfortunately it hasn't worked. I have tried all
you suggested, but nothing. There are no references 'missing' from libraries.
I have a completely new PC with the same version (2003) of Access. I don't
have it available for other users to access it yet, therefore that can't be
the problem either.
Yet, I still get the same error message when I try to open the main form.

Do you have any other suggestions?
Thanks again, for your help.

Kind regards
Rigby

 

[Allen Browne]

Do you have any control on the form that is called ImageChanged or
MouseMove?

If you open the form's module and search the code (Find on Edit menu), do
you see these words anywhere in the module?

While in the code window, what happens if you choose Compile on Debug menu?

If those things do not lead you in a productive direction, it is possible
that the database has corrupted, so try this sequence:

1. Uncheck the boxes under:
Tools | Options | General | Name AutoCorrect
Explanation of why:
http://allenbrowne.com/bug-03.html

2. Compact the database to get rid of this junk:
Tools | Database Utilities | Compact

3. Close Access. Make a backup copy of the file. Decompile the database by
entering something like this at the command prompt while Access is not
running. It is all one line, and include the quotes:
"c:\Program Files\Microsoft office\office\msaccess.exe" /decompile
"c:\MyPath\MyDatabase.mdb"

4. Open Access, and compact again.

Given the change of machines, it is also possible that there is a problem
with references that Access is not admitting. If you are still stuck at this
point, post the names of all the library references that are checked.

 

[Guest]

Dear Allen

I must apologize. I have found a possible reason for these error messages. I
think this has solved my problem. While I was waiting for my new PC
yesterday, I tried to work on my database on another older PC. Thankfully I
created a backup before hand (I do this regularly). I did not access the
backup on the older PC. So, when I opened the backup on my new PC, it worked
fine, without any errors (so far).

Hopefully this is what happened. Thank you for you help anyway.
Rigby

 

[Jeff]

I haven't had a chance to check out Rigby's suggestion
but it looks interesting.

Meanwhile one of my staff found a possible solution

it seems that Access keeps reference to OCX not only as GUID (ProdID),
but with something else (e.g. OCX file checksum).

If OCX is recompiled (even without any changes),
Access could not find new OCX using this old "reference".

To avoid this problem
- Delete all instances of corresponding .OCA ( not OCX ) file from
computer,
- Open MDB file,
- Open VBA module in design-time,
- Open form code that uses the .OCX,
- Select some event for the OCX from Access pull down
( pick an event not already in use but other than that
it does not matter which event )
- New Sub / End Sub code will be inserted by Access
- Delete this newly inserted code
- Save the module.

That's it - Access seems to reset itself and recognize the OCX again


* * Please include a copy of this message with your reply


Jeff Bennett
(e-mail address removed)


* Bennet-Tec Information Systems, Inc
* 50 Jericho Tpk, Jericho, NY 11753
* Phone 516 997 5596, Fax - 5597
* RELIABLE Components Make You Look Sharp!
* TList/Pro * ALLText HT/Pro * MetaDraw *
* Custom Software Development Services Too.
* WWW.Bennet-Tec.Com


=================== ===================