[Last Call] Learn about multicloud storage options and how to improve your company's cloud strategy. Register Now

x
?
Solved

Run Time error 13

Posted on 2009-07-06
3
Medium Priority
?
183 Views
Last Modified: 2012-05-07
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

0
Comment
Question by:IUAATech
[X]
Welcome to Experts Exchange

Add your voice to the tech community where 5M+ people just like you are talking about what matters.

  • Help others & share knowledge
  • Earn cash & points
  • Learn & ask questions
  • 2
3 Comments
 
LVL 143

Accepted Solution

by:
Guy Hengel [angelIII / a3] earned 2000 total points
ID: 24789821
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
 

Author Comment

by:IUAATech
ID: 24789904
Thanks. You are a life saver.

It looks like I will need to update the code throughout the app and append "DAO."
0
 
LVL 143

Expert Comment

by:Guy Hengel [angelIII / a3]
ID: 24789918
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

Featured Post

Industry Leaders: We Want Your Opinion!

We value your feedback.

Take our survey and automatically be enter to win anyone of the following:
Yeti Cooler, Amazon eGift Card, and Movie eGift Card!

Question has a verified solution.

If you are experiencing a similar issue, please ask a related question

Introduction In a recent article (http://www.experts-exchange.com/A_7811-A-Better-Concatenate-Function.html) for the Excel community, I showed an improved version of the Excel Concatenate() function.  While writing that article I realized that no o…
Enums (shorthand for ‘enumerations’) are not often used by programmers but they can be quite valuable when they are.  What are they? An Enum is just a type of variable like a string or an Integer, but in this case one that you create that contains…
Show developers how to use a criteria form to limit the data that appears on an Access report. It is a common requirement that users can specify the criteria for a report at runtime. The easiest way to accomplish this is using a criteria form that a…
This lesson covers basic error handling code in Microsoft Excel using VBA. This is the first lesson in a 3-part series that uses code to loop through an Excel spreadsheet in VBA and then fix errors, taking advantage of error handling code. This l…
Suggested Courses

650 members asked questions and received personalized solutions in the past 7 days.

Join the community of 500,000 technology professionals and ask your questions.

Join & Ask a Question