Run Time error 13

I see quite a few posts out there asking about "Run Time error 13", but I haven't found anything helpful so far.

Here is my scenario: My predecessor was running some VB code using Office 2003 (Microsoft Access) on a Windows 2000 server. Now, we just upgraded to Server 2008 and I am using Office 2007. When I try to run the following code, I get a "Run Time error 13 Type mismatch" error. I haven't been able to find a solution to my problem yet.

Please refer to the attached code. The OpenRecordset for tblNCLOutput works just fine. But, when I try to do a OpenRecordset on tblIndividualsAndDegrees, I get a Run Rime error 13. What gives?

And I can confirm that the table exists in the Access database.
Dim dbCur As Database
    Dim rstNCLIndividualsAndDegrees As Recordset
    Dim rstNCL As Recordset
 
    Set dbCur = CurrentDb()
    Set rstNCLOutputTable = dbCur.OpenRecordset("tblNCLOutput", dbOpenDynaset)
    Set rstNCLIndividualsAndDegrees = dbCur.OpenRecordset("tblIndividualsAndDegrees", dbReadOnly)

Open in new window

IUAATechAsked:
Who is Participating?
I wear a lot of hats...

"The solutions and answers provided on Experts Exchange have been extremely helpful to me over the last few years. I wear a lot of hats - Developer, Database Administrator, Help Desk, etc., so I know a lot of things but not a lot about one thing. Experts Exchange gives me answers from people who do know a lot about one thing, in a easy to use platform." -Todd S.

Guy Hengel [angelIII / a3]Billing EngineerCommented:
change:
Dim dbCur As Database
    Dim rstNCLIndividualsAndDegrees As Recordset
    Dim rstNCL As Recordset

into:
Dim dbCur As DAO.Database
    Dim rstNCLIndividualsAndDegrees As DAO.Recordset
    Dim rstNCL As DAO.Recordset
 
and see if that helps
0

Experts Exchange Solution brought to you by

Your issues matter to us.

Facing a tech roadblock? Get the help and guidance you need from experienced professionals who care. Ask your question anytime, anywhere, with no hassle.

Start your 7-day free trial
IUAATechAuthor Commented:
Thanks. You are a life saver.

It looks like I will need to update the code throughout the app and append "DAO."
0
Guy Hengel [angelIII / a3]Billing EngineerCommented:
to explain the issue:
both ADO and DAO have a recordset class.
if both are active in the project references, vb will silently pick 1 from them (without warning).

so, good practice is to always prefix your classes from project they are coming from.

glad I could help
0
It's more than this solution.Get answers and train to solve all your tech problems - anytime, anywhere.Try it for free Edge Out The Competitionfor your dream job with proven skills and certifications.Get started today Stand Outas the employee with proven skills.Start learning today for free Move Your Career Forwardwith certification training in the latest technologies.Start your trial today
Visual Basic Classic

From novice to tech pro — start learning today.