Microsoft Access Team Blog : No posts for the next couple of weeks...

Pick up said:

You have need of a long, long vacation: you have destroyed Access but this don't create problems to you...

You could say clearly that Access is a dead product, instead that makes us to lose time with the Ribbons!

# August 12, 2006 4:02 AM

steve said:

Looks like no comments for a while. I'm hoping you can help. I need some feedback on a A2K7 subtopic. I've been out of ms access dev for a little while. I've worked with 97/2000/2003. I remember when 2000 came out there was a big push to move from DAO to ADO, although DAO was still there if you knew where to look. If I’m reading your blog correctly, MS has gone back to DAO and is planning to stick with it as MS Access goes? If I’m working with an ADP do I still use ADO?

I guess, coming back to MS Access from VB.net the last few years, I’m a little confused about the direction on accessing data? If I’m hitting Access use DAO and if hitting SQL (with access for RAD interface) I should use ADO?

Is MS updating either of these libraries (ADO or DAO)? Also do you know if MS is looking to use ADO.net at any point for data accessing (access backend or sql) from ms access?

Thanks for the feedback. I really appreciate it.

# August 17, 2006 1:03 PM

Erik Rucker said:

Both ADO and DAO continue as peers in Access 2007. We find that for most uses, DAO works better and is preferred. However, there is some stuff that requires ADO - most noteably ADP's. The general guidance is if you're connecting to anything from an MDB or ACCDB, use DAO. If you're building and ADP solution, use ADO. We have updated DAO to support complex data, and both for things like security. At this point, we don't have any plans to support ADO.net because neither Access or our macro language are managed.

Thanks,
Erik

# August 18, 2006 3:23 PM

Rose said:

Microsoft:

"Applications that must support large populations of users, or that require very high levels of reliability or security are usually not good candidates for development in Acces"

Why Access (with SQL Server as Back-End) don't support a large number of users?
Can you give us technical details?

Why Access isn't a reliable software?

The future versions of the product will be more scalable and/or stable?

Thanks

# August 20, 2006 4:04 AM

Erik Rucker said:

Access does support large numbers of users as a front-end to SQL Server databases, and works great in that role. There are some application architectures designed for very high scale (noteably 3-tier) that Access doesn't support, but for general client-server apps Access against SQL scales very well.

As far as "why Access isn't reliable", there are a few answers. The first is that Access is highly reliable and we're constantly working to make it more so. We believe it is a great database product and one that is perfectly reliable in most applictions. There are 2 things to be aware of for large or critical applications, however. Because Access is designed to run on the desktop, it doesn't have the same commit model as SQL Server. In particular, when the database and the UI are on different machines, Access sends commits changes from the machine with the UI. If there's a network issue during the commit, this can lead to problems with the database. These issues are rare, but they do happen. SQL Server gets around the is by commiting the change from the server box itself, so there are fewer things that can go wrong between the change and the data store. The second thing is not so much software related but also covers the way the sofware is used. SQL Server boxes are managed by an administrator and generally physically secured. SQL has a rich security model and allows fine grained permissions that Access can't support. This combination of physical security for the box and a richer security model makes SQL Server more appropriate for critical applications.

As far as making Access more stable and scalable, we're definitely working on that all the time. In addition, we're doing and will continue to do extensive work to ensure that Access works great with Microsoft's servers.

Thanks,
Erik

# August 24, 2006 8:18 PM

ron cohen said:

<a href=http://viagracity.20fr.com/generic-viagra.html>buy generic viagra</a>

# September 2, 2006 11:03 AM

David G. said:

I found this on the web<a href=http://www.onlinecasinoland.20fr.com>casino online</a>.<BR>
Great fun gambling.

# September 2, 2006 11:03 AM

Szsofia said:

<a href="http://superball-keno.winbingocard.com/superball-keno.html">superball keno</a> Best Casino - 100% Download Bonus Blackjack, superball keno Progressives and much more. Play in our safe and secure environment with 24/7 SUPERBALL KENO free support, Certified Payouts, Great odds and Huge regular Bonuses!

# September 7, 2006 7:49 PM

byevet said:

<a href=http://hoosier-lottery.alltournament.org/com-hoosier-lottery.html>hoosier lottery</a> Schneider was appointed Executive Director of the Hoosier Lottery on January 13, 2005 by Governor Mitchell E. At the age of 24, she became the youngest director of advertising and public relations for a major Las Vegas Strip property, the Sands Hotel and Casino. After leaving t

# September 18, 2006 4:00 AM

Cgwsofia said:

<a href=http://mytournamentbetting.com/power-ball-lottery/power-ball-lottery-montana.html> montana lotto results see hottest coldest long overd</a> 7. Can lottery winnings be claimed by mail?
Yes. Prizes less than the jackpot amount can be claimed by mail. Jackpot winners must claim their prize in person at the Montana Lottery headquarters.
<a href=http://mytournamentbetting.com/california-lottery/california-lottery-super-lotto-result.html>california lottery</a>

# September 18, 2006 6:34 AM