2003 to 2010 Access Calendar Woes

[shepHeard]

Hi,

I've written an extensive database using Access 2003. However, not all users have the same version of Access. The database works absolutely fine with 2007, but with 2010 I get the old 'Your Database or project contains a missing or broken reference to the file 'MSCAL.OCX' version 7.0.' error. This is because I use a calendar control on a form. Then, of course I get the '2683: There is no object in this control.' error when a 2010 user clicks on the control that should launch the calendar.

The problem is what to do about it. I can't simply move to the 2010 datepicker tool, as then my 2003 users will have problems (I'm assuming the dptool is not available in 2003). The missing ref error is also very annoying, and so I can't leave it in!

Why do Microsoft do this?!? Do they really think everyone lives in some fantasy world where everyone seamlessly moves from one version of office to the next all simultaneously? And that we all have the time to re-code our databases...?

Gah.

Would a third party calendar tool be a better idea? If so, does anyone have any good ideas?

Cheers guys!

S

 

[MarkK]

Can't you just copy the mscal.ocx file to the 2010 boxes? Maybe you need to regsvr32 it. Open a command prompt, maybe with Admin priviledges, and type

regsvr32 C:\PathTo\mscal.ocx

See if that works.
The Application object also has a Version property so you can tell what version is running and selectively present stuff that works for that version.
Cheers,

 

[shepHeard]

Hi lagbolt,

Thanks for your replies

I can probably do that in theory, yes. But, it's a hassle and being as half the users are in South Africa and the rest in Australia it could be a little tricky...

I didn't know about the version property - that could definitely be useful. However, I'm not sure that would help with the missing reference errors? Can I trap them?

Cheers,

S