A "seek" problem

Not having a reference to DAO would explain why you can't declare objects as
Database or TableDef.

Having both references shouldn't matter, since the Database and TableDef
objects only exist in the DAO model, not the ADO one. Still. it's never a
bad idea to be explicit and use DAO.Database and DAO.TableDef

--
Doug Steele, Microsoft Access MVP
http://I.Am/DougSteele
(no e-mails, please!)


"Jerry Natkin" wrote in message
...

Thanks for the explanation Dirk. Would that also explain why I have
trouble declaring databases, tabledefs, etc?

Jerry

"Dirk Goldgar" wrote in
:

Both the DAO and the ADO object libraries define a Recordset object.
By default, Access 2000-2002 sets a reference to ADO and not to DAO.
Even if you later add a reference to DAO, it defaults to a lower ....

In ,
Jerry Natkin wrote:
I'd appreciate the explanation. Thanks.

Good advice. I'll follow it.

Jerry



"Douglas J. Steele" wrote in
:

Not having a reference to DAO would explain why you can't declare
objects as Database or TableDef.

Having both references shouldn't matter, since the Database and
TableDef objects only exist in the DAO model, not the ADO one. Still.
it's never a bad idea to be explicit and use DAO.Database and
DAO.TableDef