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.
Tips
How-to
News
Videos
Stories
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.
Comments: (25) Collapse
Thanks for letting us know what is going. Now, what about letting us know about any juicy new features we can expect from v2010 ? I for one would love closer integration with SQL Server as I use Access only as a backup data store for SQL records.
Thanks for the overview. Nothing I can't live without. Bonnie
http://www.dataplus-svc.com
No Great loss to my
I have always avoided the Calendar control like the plague! Good riddance Snapshot Viewer was always a poor alternative to PDF, So again no great loss. Thanks for the update
Printing of big files pdf unacceptable sluggish. Try to print out 10000 pages! Only snp!
not useful for my needs,
please give more attention to adp developers !!!
The Adp files didn't change since access 2003
Unfortunately, this may affect our moving to Access 2010. We use calendars extensively and it will require a lot of rework to change all of our Access applications that use mscal.ocx.
I don't use all those features, so not a problem for me.
@cat_matroskin: why would you want to print 10,000 pages? seems to me, you'd want a PDF of a report that someone could easily and quickly digest. Anything more than a few pages should probably stay as data. If it's a mailing address or something, you can always use the data in a mail merge.
Not a problem. . . I’m not loosing anything! but, will really like to have better integration with SQL, and gain advantages of it. Great post the one with the gauges. . Edwin
The Access 2010 "Date Picker" is way, way better than MSCAL ever was. The Date Picker just "magically" shows up next to a control (like a text box) bound to a Date/Time field (not sure how to make it show for unbound controls, though) and lets the user select a date for the control. If it's not wanted, you suppress the Date Picker by setting the control's "Show Date Picker" property to "Never" (default is "For Dates"). The Date Picker is a really cool thing -- works exactly as you'd want an "magical" control to work. So, we're finally losing that old Lotus stuff. About time! Thanks for the update, Clint!
We use Access SNP files extensively. The processing was developed long before PDF became a cost effective way to distribute reports. PDF creation used to cost an Acrobat license per creating workstation; SNP was free, included with Access. The viewer in each case is free. We can, of course, revise systems to create PDF files. But it will take several years to do it as each system reaches its overhaul/rebuild cycle. Will it delay our adoption of Access 2010? Probably not by much; we're just starting to use Office 2007 so I expect it will be about four years before the first 2010 users emerge.
to nate.granatir: > @cat_matroskin: why would you want to print 10,000
> pages? seems to me, you'd want a PDF of a report that
> someone could easily and quickly digest. We send bills (for using telephone services) to our clients by plain mail (on paper). There may be more than 300000 of those bills and each one may contain more than 1 page. We need snapshots because:
1. The technical staff that performs mass printing of bills doesn't have access to the application, where the report is created.
2. The snapshot file cannot be edited (is read-only).
3. Snapshot supports quick/easy navigation within a large report, that allows the technical staff to re-print corrupted pages in case of printer malfunction.
4. Experiments with printing PDF files showed unacceptable performance while printing large reports.
5. The size of PDF files is greater than the size of SNP files.
Is Access itself eventually going to be deprecated by MS? I have heard rumours of this online and I don't want to start developing my company's app in it if that's the case. Really I want something like Visual FoxPro :)
>Is Access itself eventually going to be deprecated by MS? I don’t think access is going anywhere! On this blog I saw the access team asking for input on features for the NEXT version of access AFTER access 2010 (which is not even out). So, access 2010 is due out this year, and I saw requests for feedback on the NEXT version after that! I think we hear this rumor every other year, and have heard this rumor for each year of the 18 year long history of ms-access! (yes, that how long it been around!!). Access received a WHOLE bunch of new features for 2010. There is all kinds of new cool goodies from an built in ribbon customizer, a new web browser control (near top in my favorite 2010 new features). Access can now create PDF’s out of reports without any any printer driver or any 3rd party software installed (nice). The data engine now for the first time has table triggers and stored procedures. This again is an MAJOR enhancement to the database engine. I love the fact that so many people cannot anymore say that ms-access lacks table triggers! Throw in new support for transparent images, round + shaded web style buttons for the interface, a new programmable navigation control system, and it quite clear that the product has gone through an MAJOR upgrade for access 2010 in look and feel and new features. On top of above features for desktop developers, you now can build web based applications with ms-access. These web based applications can be consumed by any web browser - even ones not running on a windows box. So access has now joined the whole new cloud and web dance thing! Access is rather keeping up with the times with slew of new interface features, new ability to work with the web. I am hard pressed to think of any release that has this many new features. This slew of new features represents serious development dollars and efforts into this product and thus it is quite clear that investment and support of ms-access from Microsoft is alive and well, and if anything is increasing. Thinks are looking up very well for ms-access and its future indeed... Albert D. Kallal
Edmonton, Alberta Canada
kallal@msn.com
Will Access 2010 be web aware the same way FileMaker Pro 10 is? I mean, I can put a container in a FMP layout (a "Form" in Access) and have it show a map based on the address in the record. I can track a package by the tracking number in a record and FMP shows the web page tracking result in the container. Maybe Access 2007 can already do this through some VB code hack and I just missed it. I have been learning C#/.NET so my VB is well... non-existent :)
Comments: (loading) Collapse