This post provides an overview of features and components that will be deprecated in the upcoming release of Access 2010. A decision to remove a feature or component from the product is never a trivial one; we therefore have put a lot of thought when deciding to remove functionality. We believe it will benefit the majority of our customers by helping us to make forward progress.
Microsoft recommends that when you develop new Access applications, upgrade or modify existing applications, avoid using and remove these deprecated features and components.
Here’s a list of deprecated features and some workarounds you can use. We would love to get your feedback and experience with the workarounds.
Calendar Control (mscal.ocx)
The calendar control is not shipped in Access 2010 for a number of reasons. If you open a form that has mscal.ocx and you will see the following error: “Your Microsoft Office Access database or project contains a missing or broken reference to the file ‘MSCAL.OCX’.”
To fix this issue, you will need to remove this from your application. Here are some alternatives:
- Use datepicker. Here is an example on the datepicker- http://office.microsoft.com/en-us/access/HA102835451033.aspx
- Use other 3rd-party calendar controls that are available on the Web. Here are a couple of community provided calendar controls:
In Access 2010, snapshot format for reports will not be available.
As an alternative, you can export your reports to PDF/XPS and Excel formats instead. This is native functionality that doesn’t require a download.
Data Access Pages (DAPs)
In Access 2007, we partially deprecated DAPs. Users could not design them, but they could execute them. In Access 2010, DAPs are completely removed. Users will not be able to design and execute them. They will be enumerated in navigation pane but if user attempts to open them, they will see the following error: “Microsoft Office Access does not support this operation for Data Access Pages. To perform this operation, use Microsoft Office Access 2007 or earlier.”
DAPs will continue to be stored in databases and round-tripped to down-level versions on save. You can use older versions of Microsoft Access to use them.
Paradox (3, 4, 5, 6, 7) ISAM, Lotus 1-2-3 ISAM and Red 2 ISAM or Jet 2
Export, import and linking to data from Paradox 3, 4, 5, 6, 7, Lotus 1-2-3, Access 1.0 and 2.0 (Red 2, or Jet 2) will not be available in Access 2010. User may see the following error: Installable ISAM not found.
You will need Access 2007 or older in order to be able to export, import or link data from Paradox 3, 4, 5, 6, 7, Lotus 1-2-3, Access 1.0 and 2.0 (Red 2, or Jet 2) files.
Replication conflict Viewer
In Access 2007 and before, we shipped Replication Conflict Viewer that enables the user to visually display synchronization conflicts and enable resolution. This will not be shipped in Access 2010.
As a workaround, you can write your own custom conflict resolution functions and mark them on the ReplicationConflictFunction property in the database replica set. Here is a link that describes how to set property so that you can create a custom procedure to resolve conflicts- http://support.microsoft.com/kb/158930.
There are several code samples for resolving replication conflicts available on the Web.