> Thanks for posting your solution. It is rather interesting that
> reregistering DAO 3.6 would fix the problem with A2007.

Signature
David W. Fenton http://www.dfenton.com/
usenet at dfenton dot com http://www.dfenton.com/DFA/
>> Thanks for posting your solution. It is rather interesting that
>> reregistering DAO 3.6 would fix the problem with A2007.
>
>Well, doesn't A2K7 use DAO 3.6 for MDB files?
I would've thought A2007 would use the ACE DLLs. Which, BTW, is DAO
12. See C:\Program Files\Common Files\Microsoft Shared\OFFICE12 for
the set of DLLs if you have A2007 installed.
ACE being the updated name for Jet.
Tony

Signature
Tony Toews, Microsoft Access MVP
Please respond only in the newsgroups so that others can
read the entire thread of messages.
Microsoft Access Links, Hints, Tips & Accounting Systems at
http://www.granite.ab.ca/accsmstr.htm
David W. Fenton - 03 Apr 2007 17:51 GMT
>>> Thanks for posting your solution. It is rather interesting that
>>> reregistering DAO 3.6 would fix the problem with A2007.
[quoted text clipped - 6 lines]
>
> ACE being the updated name for Jet.
Is it not the case that MDB files are Jet 4? And that it uses a
slightly-altered version of the DAO library based on DAO 3.6? My
understanding is that there is a separate DAO library for the ACE
(i.e., the successor to Jet 4), but just thinking about it, maybe
there's a single DAO library that covers both versions of Jet?
I'm interested in finding out about this. Can you (or someone else
with A2K7) do a little investigating?
One question: what happens when you open an A2K3-created MDB? Does
it retain the DAO 3.6 reference or silently substitute the new DAO?

Signature
David W. Fenton http://www.dfenton.com/
usenet at dfenton dot com http://www.dfenton.com/DFA/