CDaoQuerydef and CDaoRecordset; running a query help

Posted on 1998-08-26
Medium Priority
Last Modified: 2013-11-19
I'm trying to do a simple search through my database.  I created a query in Access called "Simple Search".  The Criteria is: [Title] like [Search String].  Title is a field in the database.  Search String is a parameter that is set by my program.  This is my code:

//m_pDaoWorkspace and m_pDaoDatabase have already been created

CDaoQueryDef q(m_pDaoDatabase);
q.Open("Simple Search");
int isRet = q.GetReturnsRecords(); // this returns 1
int param = q.GetParameterCount(); // this returns 1
CDaoParameterInfo info;
q.GetParameterInfo(0,info);  // the 1 param = Search String

q.SetParamValue("Search String",COleVariant("*Uranium*"));
//I hope I have done this right.This might explain problem

CMyRecordset *r; // derived from CDaoRecordset
r = new CMyRecordset( m_pDaoDatabase );

if( ! r->IsOpen( ))
   catch( CDaoException* eDaoException )
      eDaoException->Delete( );
      return FALSE;
int recs = r->GetRecordCount();

This last line is the problem.  it returns 0.

If I do not pass the CQueryDef pointer to the Open function of CMyRecordset and just open it as a normal dynset recordset GetRecordCount returns 220 as it should.  There are 220 records in the database.  So the problem lies in my CQueryDef usage and most likely, I figure how I set the parameter.  Because if I run the query in MS-Access with the same value as I set it in my program it returns some 50 records.

I'd really appreciate any information I could get about things to look at.
Question by:LukeSkywalker

Accepted Solution

milenvk earned 800 total points
ID: 1321329
Yes the problem is where you suppose it is. DAO uses ANSI character strings, but COleVariant converts your "*Uranium*" parameter to BSTR (i.e. wide character string). Here's what you should do to fix the problem. Replace the line:

q.SetParamValue("Search String",COleVariant("*Uranium*"));


q.SetParamValue("Search String",COleVariant("*Uranium*", VT_BSTRT));

See VT_BSTRT is the BSTR type that uses ANSI convension. VT_BSTR is the one that's using the wide character convension and it is set by the COleVariant contrustor by default.


Author Comment

ID: 1321330
You suggestion worked to solve that problem.  Thank you!

Featured Post

Free Tool: Site Down Detector

Helpful to verify reports of your own downtime, or to double check a downed website you are trying to access.

One of a set of tools we are providing to everyone as a way of saying thank you for being a part of the community.

Question has a verified solution.

Are you are experiencing a similar issue? Get a personalized answer when you ask a related question.

Have a better answer? Share it in a comment.

Join & Write a Comment

Introduction: Database storage, where is the exe actually on the disc? Playing a game selected randomly (how to generate random numbers).  Error trapping with try..catch to help the code run even if something goes wrong. Continuing from the seve…
Ready to get certified? Check out some courses that help you prepare for third-party exams.
This video will show you how to get GIT to work in Eclipse.   It will walk you through how to install the EGit plugin in eclipse and how to checkout an existing repository.
To export Lotus Notes to Outlook PST or Exchange and Domino Server files to Exchange Server or PST files with ease, go for Kernel for Lotus Notes to Outlook conversion tool. Through the video, you can watch the conversion process. A common user with…

622 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