Run-time error on Calendar click

[Jeff via AccessMonster.com]

Strange thing just happend. My Calendar form was working fine and all of a
sudden I'm getting a run-time error:

"Method 'Value' of object '_CustomControl' failed.

My code is crashing on:

Forms!Calendar!Calendar.Value = Date

Any ideas?

 

[Jeff via AccessMonster.com]

Strange thing. I just tried running the database from home through terminal
services and it runs fine. Could something have been changed with my Access
settings on my system at work? Such as corrupt dll file? I'll have to run
some further testing on Monday.

 

[Sylvain Lafontaine]

Did you copy this database beetween two different versions of Windows?

Check your references and make sure that they are OK. If necessary,
decompile/recompile the database, particularly when you want to move it to
another system. The slightest change in version, for exemple in one of the
service pack, may give you this problem if you don't force a recompilation
of the whole thing.

(For decompiling, you can use the /decompile switch from a link. You can
also do it without using this switch by adding a dummy reference in the VBA
application, closing the dialog window to make sure that Access take notice
of the change, then reopens it and remove the reference previously changed.)

 

[Philipp Stiefel]

(For decompiling, you can use the /decompile switch from a link. You can
also do it without using this switch by adding a dummy reference in the VBA
application, closing the dialog window to make sure that Access take notice
of the change, then reopens it and remove the reference previously changed.)

I ran into some issues with adding/removing library-references
in a large Access-App with lots of references, which indicate
that it will not force Access to decompile the whole code in
every case, especially if there already are issues with some
parts of the compiled code.
Hence I recommend just using the decompile-switch for complete
decompilation!

Cheers
Phil

 

[Jeff via AccessMonster.com]

Turns out the corruption issues was only on my local system. I was able to
narrow down the cause as a recent installation of an HR application that I
have been testing. Appears the installation re-mapped some dll files.