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.
After a long, hard effort the stars have finally aligned. The Access Developer Extensions team is very happy to announce the release of the Access 2007 Developer Extensions and the Access 2007 Runtime.
Updated Jan 2009: Here is the latest link to the 2007 Developer Extensions
Here is the link for the 2007 Access Runtime:
Thanks for the release and your efforts.
A suggestion, why not to have a single file, bundled, where the access runtime have all the dll's and licenses, as we then start our msaccess app with something like "msaccessLocalFileBundled.exe ourApp.mde". This will not make interferences if the client already have an other version of office installed.
Great news, but I am only finding the English versions. Any idea when the localized versions will be available? Klaus
Excellent news, and many thanks for the team's hard work in releasing this crucial tool. Long live Access!
Problems getting Access Runtime:
The download you requested is unavailable. If you continue to see this message when trying to access this download, go to the "Search for a Download" area on the Download Center home page.
I 2nd the error on Access Runtime download: The download you requested is unavailable. If you continue to see this message when trying to access this download, go to the "Search for a Download" area on the Download Center home page.
The reason for the error - the runtime has been pulled. See quote from Clint Covington's blog (blogs.msdn.com/clintcovington) Ug. It turns out that there was a bad bug in one of the Access Runtime components. After we released the Access Runtime yesterday it was discovered that Microsoft Update didn’t automatically detect and patch this component. We unfortunately had to pull down the Access Runtime download until we can ensure that all components can be patched by Microsoft Update. We are sorry for the inconvenience, and we hope to have it back up in a few weeks. If you happen to be one of the lucky few to download the Access Runtime, please hold off on deploying it to your customers until we get all the Microsoft Update kinks worked out.
I'm confused why 1.) this wasn't tested more thoroughly, and 2.) why this blog doesn't have an update on the situation. It's not like this is a beta product. Access 2007 has been out for months and the runtime still isn't right.
Your confusion is justified. I can promise you that no one is more let down by this unfortunate turn of events than the Access team. The issue in question is not an issue with the Access Runtime itself, but instead with one of the components we depend on and install with Access. We only received word today from the team who owns that other component that there was cause for concern. We're working hard to get the update we need in place so that we can re-release the runtime package. We should have it in place within a few weeks time. Thank you all for your patience. I know this is a big inconvenience, and rest assured the Access team is doing absolutely everything humanly possible (including tapping people who are supposed to be working on v14) to get this taken care of -right now-. Zac Woodall
A few WEEKS ??? This whole thing gets really embarrassing...
few weeks according to Microsoft Time. regards
It would be nice that instead of:
'The download you requested is unavailable...'
MS actually displayed a page explaining that the runtime was pulled and will be delayed.
Zac, be a champ and place a note on the Access homepage that the runtime has been pulled. The only place I found out of this issue - and what was being done about it - was via this one little blog. I'm sure Marketing won't find. For those whom already have the runtime, what damage is going to be caused if they release it to their clients prior to the fix? Out of curiosity what is being done to make these developers aware of this issue? "Damn the team who owns the other component!" I bet your boss isn't going to be shouting you beers this Friday eh Zac?
To Carl ("This whole thing gets really embarrassing..."):
IMO, they should have not released MSO 2007, they'd better wait for 2008... or maybe 2009... so that they had some time to fix old bugs. Never mind... I'm going to try A2007 CZ trial soon. But I'll not buy MS Office 2007 Professional before SP2 so that Acces team has a lot of time to test ADE & runtime. I hope Microsoft will prolong tech-support for MSO 2007.
Since I've been waiting for runtime and ADE all the way back when Office 2007 was in beta releases, this has made me very sad... I've managed to download the runtime and ADE, I've been trying to use it just in case if it can get me through completeing my current Access2007 project. If someone is interesting what were the bugs, I've found a few of them. I'm note sure if they classify for the runtime, but I've compared the same Access solution on two virtual machines with plain Windows XP SP2 without anything else on it. One had installed full Access 2007 and the other had Access 2007 runtime. Full access 2007 worked without any problems and it served as comparsion for runtime applications.
* tested solution is an Access Data Project (ADP) / ACCDR (on runtime, created with ADE) Two key things that I've encounterd with the runtime:
1.) report that was bound to sql server view reported error 2580 - record source specified does not exist, and I'm sure it exists because the underlaying form runs on the same view, and this works as it should on full Access 2007 2.) I have a subform that is bound to the result set of a stored procedure, parameters for the stored procedure are on the master form. Subform is requeryed when any of the parameters are changed. This works on full Access 2007, and on runtime, nothing happens, not even an error message or someting like that, subform just isn't requeried. I compared the same thing with full access 2007 running with /runtime command line arguments and it worked as it should. Today, I went looking for a solution and I saw that Access 2007 runtime and ADE has been pulled off, so I'll stop with trying to resolve this issues since I think that this is all related to "the pull off". I would be glad if Microsoft provided the concrete reasons why this happened (the pull off). Anyway, I think that these issues should have been tested before the release, even though the relase came so late. Now I've spent few hours trying to make something work, instead of spending my time on variuous other projects that I'm involved with, and I think that if this isn't resolved quickly enogh, I'll move all my ongoing Access projects to .Net, Smart Client Factories and the real architecture that works on my other projects without relying on promises of excelent new "runtime" versions... In the time that I've spent waiting for this release, I could have created the whole project on .Net, C#, CAB, SCSF and other technologies/practices that definitively need more time for development but surely provide many benefits compared to Access 2007, at least a stable roadmap that I can sync with my investors wishes. Sincerly, pw
Put a better message or update the blog stop wasting our time.