By using this site, you agree to our updated Privacy Policy and our Terms of Use. Manage your Cookies Settings.
424,946 Members | 712 Online
Bytes IT Community
+ Ask a Question
Need help? Post your question and get tips & solutions from a community of 424,946 IT Pros & Developers. It's quick & easy.

DAO360.DLL - Access 2007

P: n/a
Is there any advantage for using "Microsoft Office 12.0 Access
Database Engine Object Library" instead of DAO360.DLL for Access 2007 ?

Mar 14 '07 #1
Share this Question
Share on Google+
1 Reply


P: n/a
When you create/open an ACCDB, Access 2007 uses the ACEDAO.DLL library which
supports the functionality you need for ACCDB. In code, VBA recognises this
as the DAO library.

When you create/open an MDB in Access 2007, it uses the DAO360.dll library
which supports the functionality appropriate for MDB. In code, VBA
recognises this as the DAO library.

You can verify this by opening the Immediate Window (Ctrl+G) and entering:
? References("DAO").FullPath

It doesn't make sense to try to use DAO360.dll for an ACCDB, since you would
run into trouble with the new things like complex data types listed at the
end of this article:
http://allenbrowne.com/func-06.html

--
Allen Browne - Microsoft MVP. Perth, Western Australia
Tips for Access users - http://allenbrowne.com/tips.html
Reply to group, rather than allenbrowne at mvps dot org.
"Chris" <CL*****@gmail.comwrote in message
news:11**********************@p15g2000hsd.googlegr oups.com...
Is there any advantage for using "Microsoft Office 12.0 Access
Database Engine Object Library" instead of DAO360.DLL for Access 2007 ?
Mar 14 '07 #2

This discussion thread is closed

Replies have been disabled for this discussion.