Hi all,

   I writed a database program with ADO. The statements I
used are below:

   HRESULT hr;
   _ConnectionPtr pConnection;
   _RecordsetPtr pRecordset;
   try
   {
      hr=pConnection.CreateInstrance("ADODB.Connection");
      if (SUCCEEDED(hr))
           pConnection->Open("....",....);
   }
   catch(_com_error e)
   {
      CString eMsg;
      eMsg.Format("Can't connect to database, error is %s\
                   ",e.Description);
      AfxMessageBox(eMsg);
   }
   ....

   When I run this program, It can't connect to database
due to some reasons.I want to use the statements above to
show the error message, but it showed the message with
wrong code and not to showed correctly.
   Can you help me solve the problem.
   Thanks.

                                                 Dj

The function _com_error::Description returns a _bstr_t, and you can't
pass it to the ellipsis parameter in CString::Format. Try casting it
to LPCTSTR, which should invoke the appropriate _bstr_t operator
char/wchar_t* to match the CString %s format specifier.

--
Doug Harrison
Microsoft MVP - Visual C++

Dj,

The Description in the _com_error object is a method not a property....

this line of code will yield garbage:
/* ********************* */
eMsg.Format("msg text%s",e.Description);

/* ********************* */

For nonUnicode build try this (verbose form) instead:
/* ********************* */
_bstr_t errd(e.Description());
eMsg.Format("Can't connect to database, error msg is:\n%s",(char *)errd);

/* ********************* */

best regards
roy fine

Personally, my favorite is:

   catch(_com_error e)
   {
      CString eMsg;
      eMsg.Format("Can't connect to database, error is %s\
                   ",static_cast<LPCTSTR>(e.Description()));
      AfxMessageBox(eMsg);
   }

This compiles in unicode and ANSI builds.  Unfortunately, it's also possible
for it to crash, as if _bstr_t contains a NULL BSTR, this returns a NULL for
the cast.

You'll have to add appropriate checks to make sure that there actually is a
description in there.  I'll leave it to you to come up with some ingenious
code for that.

You might also want to consider the case where Description is empty, but
ErrorMessage has useful information.