Re: Using ADO and DAO in same mdb
- From: "David W. Fenton" <XXXusenet@xxxxxxxxxxxxxxxxxxx>
- Date: Mon, 30 Jul 2007 13:40:47 -0500
John Winterbottom <john.wb@xxxxxxxxx> wrote in
news:5h64mnF3j9nppU1@xxxxxxxxxxxxxxxxxx:
Be aware that schema changes made through an ADO connection in
this way are not always immediately visible in DAO unless you
refresh the collection you're working with.
If you use a db variable initialized with CurrentDB() *after* the
collection has been updated, you won't need to refresh, as
CurrentDB() refreshes collections before returning its reference
(that's why it's slower than DBEngine(0)(0)).
On the other hand, if you use a db variable that was initialized
with CurrentDB() before updating the collections, you'll need to
refresh the appropriate colection, as John advises.
--
David W. Fenton http://www.dfenton.com/
usenet at dfenton dot com http://www.dfenton.com/DFA/
.
- References:
- Using ADO and DAO in same mdb
- From: Barry Edmund Wright
- Re: Using ADO and DAO in same mdb
- From: John Winterbottom
- Using ADO and DAO in same mdb
- Prev by Date: Re: Using ADO and DAO in same mdb
- Next by Date: Re: open Form ontopmost of all windows
- Previous by thread: Re: Using ADO and DAO in same mdb
- Next by thread: Toolbar not working
- Index(es):
Relevant Pages
|