You can use your favorite social network to register or link an existing account:
Or use your email address to register without a social network:
Sign in with these social networks:
Or enter your username and password
Forgot your password?
Yes, please link my existing account with for quick, secure access.
No, I would like to create a new account with my profile information.
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.
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:
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.
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.
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.
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.
>have it show a map based on the address in the record. In acces 2010, this is easy with the new web contorl we have. The new web browser control in access allows one to use a column from the database that is an URL to an web site. So you can store an url that represents and displays the the map location, or create an expression that represents an URL for taracking. Take a look at the following video of mine for access 2010. Note in the video how I display the current weather (temperature) for the current location. This was accomplished by dropping in the web browser control, and then binding the control to a column in the database with the URL for that location. www.youtube.com/watch The new web browser control works for both client (VBA) applications, or 100% browser based applications you build in ms-acces. So, yes you can do this in 2010, and you don't need any code at all. You are free to use code to "create" the URL that feeds the display in the form if you wish.
Thanks for the heads up. I am sure that there will be some cool new features that we can use to enhance existing Access solutions.
OTOH, please, make reports editable (eg. Word-format). That would be great enhancement. But don't forget to export all the graphics! Current export to RTF is just a joke. :-(
Q: Whether it is limited to 2 gigabytes not only database but also other files, for example the files received as a result of export of reports in XPS, PDF formats and on temporary work files?
I was try to find the chart control is gone WTF
I would like to see better integration between Access Reports and Powerpoint. I need to create frequently changing presentations that could have the data and images fed from Access.
Whose idea was it to eliminate the Calendar control? I agree that it isn't needed for forms but what about in reports? I have a dashboard that contains six calendars for these dates: Document Received, Questions Due Date, Review Date 1, Review Date 2, Ship Date, and Document Due Date. Will it be possible to use the OCX that is now in 2007 in AC2010? Also, has the export-to-RTF feature been fixed? Or better yet, does 2010 export to standard Word files? Now the exporter moves text wherever it likes and even drops text willy-nilly. It can't be trusted. And have you implemented WBS codes in 2010? I have had to create workarounds for this since 2003. Thanks. David
Snapshot gone? Bad move.... So many things disappearing. I download invoices from a vendor every morning......pdf... Takes SO long its frustrating...Thats why I use Snapshot. I am hearing a call for web based apps.. Not for mega money corporations with sharepoint... For small to medium size businesses. By the 2010 version we could have had a very nice little program for creating online DB's... BUT... MS is stuck on integrating a nicely priced program (Access) with mega dollar program (sharepoint), out of the reach of most small to medium businesses.
And nothing here for developers... Except the desire to move to another product.
All my App's also deals with mscal.ocx and can't find solution for taht except rebuilding those again.
This Visual How To Article refers to a sample Access 2010 database called CalendarDemo.accdb that contains a form that can be used to replace the calendar control no longer supported in Access 2010. Efforts to date have failed to discover how we can obtain this sample. Any Ideas? I have an Access 2003 system that heavily relies on the old control, now disabled by this change. Here's the article: msdn.microsoft.com/.../gg251104.aspx.