Fixing Reference problem

[Alex Motilal]

Hello everybody.
I have installed Office 2010 in my system. The MS Access Databases developed in earlier versions are not opening properly. I get the following Message:
Your Database or project contains a missing or broken reference to the file 'MSCAL.OCX' version 7.0.
To ensure that your database or project works properly, you must fix this reference.
Please help.
With thanks


Alex

[ajetrumpet]

mscal.ocx comes installs in the root folder of office 2007, so maybe check that same folder for your version of office and see if it's there? the root folder is probably "office13", via:

C:\Program Files\Microsoft Office\office13

it may have changed or been eliminated for the newer version of office. it also may have had it's named changed. It only has 3 classes of objects in it, from what I can see of it. Are you using calendar controls via active x?

[Alex Motilal]

Thank u Adam.
I shifted back to Office 2007. Can u tell me what advantage Access 2010 has over 2007?
Alex

[ajetrumpet]

Thank u Adam.
I shifted back to Office 2007. Can u tell me what advantage Access 2010 has over 2007?
Alex

I don't know them all. Mostly I'm guessing the web-based forms. People talk a lot about those. Also, I think sharepoint is easier to work with.

I was going to suggest that if you were using that .ocx library for just one calendar control, to simply use another one in the 2010 active x library, but I guess yoiu've already solved the problem.

[Alex Motilal]

Thanks.
I solved the problem by downloading and installing the file. However, I shifted back to Access 2007. In intend to use Access 2010 after knowing all about the new features.
Alex

[pkstormy]

Ahh....Yes, in Microsoft's infinate wisdom, they did away with the MSCal.ocx in MSAccess 2010. One of the most idiotic things they've done besides moving around all the menu items so MSAccess veterans spend half the time finding where they put everything.

There's a few other 'nicety' things they've done in 2010 to make an MSAccess veteran developer's life more complex.

[ajetrumpet]

Ahh....Yes, in Microsoft's infinate wisdom, they did away with the MSCal.ocx in MSAccess 2010..

Fashionably late as always, and after the problem is solved.

But at least we know now that the ocx WAS actually cut from the inventory! Thanks Stormy!