Access 2010: Overview of deprecated features and workarounds

Microsoft listed features and components deprecated in Access 2010, and recommends that “when you develop new Access applications, upgrade or modify existing app, avoid using and remove these features”. Here’s a quick list of deprecated features and workarounds:Calendar Control isn’t shipped, when you open a form with mscal.ocx, you’ll see error: “Your Microsoft Office Access […]

Microsoft listed features and components deprecated in Access 2010, and recommends that “when you develop new Access applications, upgrade or modify existing app, avoid using and remove these features”. Here’s a quick list of deprecated features and workarounds:

  • Calendar Control isn’t shipped, when you open a form with mscal.ocx, you’ll see error: “Your Microsoft Office Access database or project contains a missing or broken reference to the file 'MSCAL.OCX’.” To fix, remove this from your app. Some alternatives: Use a datepicker, or other 3rd-party calendar controls here, or here.
  • As an alternative to “Snapshot Format”, you can export your reports to PDF/XPS and Excel formats instead.
  • Users willn’t be able to design and execute Data Access Pages (DAPs). 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.
  • 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) willn’t be available. User may see: Installable ISAM not found. You’ll need Access 2007 or older in order to excecute them.
  • As a workaround to “Replication conflict Viewer,” you can write custom conflict resolution functions and mark them on ReplicationConflictFunction property in database replica set. Refer KB158930.

[Source]