Solved

Vb for Access code not work

Posted on 2004-08-30
5
227 Views
Last Modified: 2013-11-27
I am using the following code (which is the same as i used in another database) but it stops at set rstCLP    saying run time error 13 type mismatch

   'add DAO 3.6 object library
   
    Dim rstDB As Database
    Dim rstCLP As Recordset
    Dim rstSumm As Recordset
     
    Set rstDB = CurrentDb
   
    Set rstCLP = rstDB.OpenRecordset("SELECT * FROM CLP")
    Set rstSumm = rstDB.OpenRecordset("SELECT * from CLPSummary")

CLP and CLPSummary are valid tables (linked) in the current database.  My plan is to read from the CLP table and write to the CLPSummary table
0
Comment
Question by:jimcrint
5 Comments
 
LVL 5

Expert Comment

by:rsriprac
ID: 11937467
Could you try the following:

    Dim rstDB As New Database
    Dim rstCLP As  New Recordset
    Dim rstSumm As  New Recordset

   
   rstDB = CurrentDb
   
   rstCLP = rstDB.OpenRecordset("SELECT * FROM CLP")
   rstSumm = rstDB.OpenRecordset("SELECT * from CLPSummary")

-Ram
0
 
LVL 44

Accepted Solution

by:
Arthur_Wood earned 250 total points
ID: 11937614
try this change (I assume that you are using this code in Access 2000+):

   Dim rstDB As New Database
    Dim rstCLP As  New DAO.Recordset
    Dim rstSumm As  New DAO.Recordset

   
   Set rstDB = CurrentDb
   
   Set rstCLP = rstDB.OpenRecordset("SELECT * FROM CLP")
   Set rstSumm = rstDB.OpenRecordset("SELECT * from CLPSummary")


ADO is the default Data Access Technology in Access 2000 ( and newer) and thus a Recordset is declared as ADO.Recordset by default.  An ADO recordset is a DIFFERENT TYPE from a DAO Recordset, hence the Type Mismatch.

AW
0
 
LVL 1

Author Comment

by:jimcrint
ID: 11938198
The DAO was the answer but the new in the declarations were not allowed or required in this context.

I am now able to access the tables and manipulate the data to my hearts content

Thank you
0
 
LVL 44

Expert Comment

by:Arthur_Wood
ID: 11938288
that is correct, in fact, the use of New in a Declaration is NOT a good idea, and I should have noticed that.  I simply Cut and Pasted the previous suggestrion, and changed the declaration to DAO. for the recordset object.  Am I baaaaad or what - wasn't looking carefully.

Glad you have resolved the issue.  Glad to be of some small measurwe of assistance.

You can accomplish the same end result, by moving the DAO reference ABOVE the ADO reference, or by deleting the ADO reference altogether (Tools/References).

AW
0
 
LVL 19

Expert Comment

by:akoster
ID: 11939748
maybe you could use a

SELECT * INTO CLPSummary FROM CLP WHERE ....


clause ?
0

Featured Post

Get up to 2TB FREE CLOUD per backup license!

An exclusive Black Friday offer just for Expert Exchange audience! Buy any of our top-rated backup solutions & get up to 2TB free cloud per system! Perform local & cloud backup in the same step, and restore instantly—anytime, anywhere. Grab this deal now before it disappears!

Join & Write a Comment

Overview: This article:       (a) explains one principle method to cross-reference invoice items in Quickbooks®       (b) explores the reasons one might need to cross-reference invoice items       (c) provides a sample process for creating a M…
A short article about problems I had with the new location API and permissions in Marshmallow
In Microsoft Access, learn the trick to repeating sub-report headings at the top of each page. The problem with sub-reports and headings: Add a dummy group to the sub report using the expression =1: Set the “Repeat Section” property of the dummy…
In Microsoft Access, when working with VBA, learn some techniques for writing readable and easily maintained code.

760 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

Need Help in Real-Time?

Connect with top rated Experts

21 Experts available now in Live!

Get 1:1 Help Now