Access 2003 Calendar Control

[redbull]

Scenario:


There is an application that was originally developed in 2003. This application has multiple connections to SQL databases, and has a LOT of queries on it.... All of these elements rely on the access 2003 calendar....

Problem:
Against all advice some of the users updated to access 2010, rendering the 2003 calendar control useless... and wouldn't ya know it... now they can not run their reports.

----------------

My question is this, I REALLY don't want to (even know where all of them) change all these stored procedures, there are so many of them I cannot count... is there a work around for this? What would you do in my situation? Only thing I've been able to think of is Drink.

[June7]

Define 'stored procedure' - VBA code, Access query?

There are third party calendar controls that can be added into db (never done that).

Review http://msdn.microsoft.com/en-us/library/gg251104.aspx

Rick Fisher's Access Find & Replace might help you modify the Access code and objects. It has saved my butt numerous times and costs only about $50.

[redbull]

Stored procedures on sql databases, many of them. Basically, these reports (about 20 of them) all run off one main switchboard type form. So hundreds of queries, reports and metrics rely on this forms!frmMain!.cal item.

[June7]

Fisher's tool could help with the edits of Access objects and code but the SQL stored procedures is beyond me.

But how much really needs to change? Replace the form calendar control named cal with another control using the same name.