ARGH! Type Mismatch on Set Recordset

[Jozef]

Hello,

I hope someone can help, because I"m pulling my hair out! (and I need all
the hair I can get).

I have the following code;

Option Explicit
Option Compare Database

Sub TestItems()
Dim rst As Recordset
Set rst = CurrentDb.OpenRecordset("TestTable")
End Sub

And when I run this code in A2K2 with DAO 3.6 included in the references, I
get a Type Mismatch error.

Any idea what's up with that?

Thanks!

[Tom van Stiphout]

On Wed, 24 Aug 2005 03:12:03 GMT, "Jozef" <SP**********@telus.net>
wrote:

Perhaps you have another reference (ADO comes to mind) that defines a
recordset object. Disambiguate as follows:
Dim rst As DAO.Recordset

Btw, be explicit about what recordset you want to be returned by
OpenRecordset. E.g.:
Set rst = CurrentDb.OpenRecordset("TestTable", dbOpenSnapshot)

-Tom.

Hello,

I hope someone can help, because I"m pulling my hair out! (and I need all
the hair I can get).

I have the following code;

Option Explicit
Option Compare Database

Sub TestItems()
Dim rst As Recordset
Set rst = CurrentDb.OpenRecordset("TestTable")
End Sub

And when I run this code in A2K2 with DAO 3.6 included in the references, I
get a Type Mismatch error.

Any idea what's up with that?

Thanks!

[Jozef]

Thanks Tom,

That worked, but I'm wondering why I never encountered that before?
"Tom van Stiphout" <no*************@cox.net> wrote in message
news:vq********************************@4ax.com...

On Wed, 24 Aug 2005 03:12:03 GMT, "Jozef" <SP**********@telus.net>
wrote:

Perhaps you have another reference (ADO comes to mind) that defines a
recordset object. Disambiguate as follows:
Dim rst As DAO.Recordset

Btw, be explicit about what recordset you want to be returned by
OpenRecordset. E.g.:
Set rst = CurrentDb.OpenRecordset("TestTable", dbOpenSnapshot)

-Tom.

Hello,

I hope someone can help, because I"m pulling my hair out! (and I need all
the hair I can get).

I have the following code;

Option Explicit
Option Compare Database

Sub TestItems()
Dim rst As Recordset
Set rst = CurrentDb.OpenRecordset("TestTable")
End Sub

And when I run this code in A2K2 with DAO 3.6 included in the references,
I
get a Type Mismatch error.

Any idea what's up with that?

Thanks!

[David W. Fenton]

"Jozef" <SP**********@telus.net> wrote in
news:wn%Oe.298308$5V4.48308@pd7tw3no:

That worked, but I'm wondering why I never encountered that
before?

Well, it's perhaps the fault of Microsoft for engineering A2K
stupidly to have newly-created MDB files include the ADO reference
but not the DAO record. On the other hand, files converted from A97
will include the DAO reference and no ADO reference. If you're
accustomed to working with converted MDBs, you likely would never
have encountered the missing DAO reference.

Microsoft has recognized the error of their ways and changed the
behavior in A2K3, if I'm not mistaken, to include DAO.

Either way, given the possibility of having both ADO and DAO
references (there are perfectly valid reasons for that), it's best
to disambiguate your uses of DAO and ADO object types as Tom
suggested.

I *never* use ADO, but I always explicitly indicate that I'm using
DAO, just in case my code should ever end up running in an
environment with an ADO reference that happens to be in the wrong
order.

--
David W. Fenton http://www.bway.net/~dfenton
dfenton at bway dot net http://www.bway.net/~dfassoc

[Douglas J. Steele]

"David W. Fenton" <dX********@bway.net.invalid> wrote in message
news:Xn**********************************@216.196. 97.142...

"Jozef" <SP**********@telus.net> wrote in
news:wn%Oe.298308$5V4.48308@pd7tw3no:

That worked, but I'm wondering why I never encountered that
before?

Microsoft has recognized the error of their ways and changed the
behavior in A2K3, if I'm not mistaken, to include DAO.

True, but the ADO reference is higher in the list than the DAO reference, so
you definitely need to disambiguate declarations of DAO recordsets. (On the
other hand, I explicitly reference them even in Access 97, just so it's
obvious.)

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