RE: [bdbxml] asString

"Chun, Nathan" <[email protected]>
Newsgroups gmane.comp.db.dbxml.general
Message-ID <5283566E2D520A478CD58729DB4EAB3F03B07C86@XCGCAK01>
Thanks for the Info.  I used both of suggestions, and this solved the
problem.

 

Thanks again

 

Nathan

 

  _____  

From: Rick Ekle [mailto:Rick.Ekle-jnKy7PRZcq8n/[email protected]] 
Sent: Tuesday, June 21, 2005 8:21 AM
To: [email protected]
Subject: RE: [bdbxml] asString

 

Go to Project Settings, C/C++, Code Generation and look at the Runtime
Library setting.  Make sure you have the same setting here that DBXML
uses in their project.  For my application, I use:

 

Debug: Multi-threaded Debug DLL

Release: Multi-threaded DLL

 

And it works well.

 

Rick

 

 

  _____  

From: adrian [mailto:[email protected]] 
Sent: Tuesday, June 21, 2005 10:08 AM
To: [email protected]
Subject: [SPAM] - RE: [bdbxml] asString - Email found in subject

 

You could try compiling everything with the _DLL pre-processor
directive.  This worked for me a while ago.  I had a
_CrtIsValidHeapPointer exception thrown on similar operations and it was
due to objects allocated on a dll heap being destroyed on the
application heap.  I think that this switch forces all code to use the
local application heap and came across it after digging through the CRT
source.  

I am no expert on this stuff but it did get rid of the problem. I was
using Visual Studio .NET 2003.  Another recommendation at that time was
ensure everything was compiled with the same switches (presumably do no
mix and match debug and release code) but this didn't help.

 

Regards,

Adrian.

  _____  

From: Chun, Nathan [mailto:[email protected]] 
Sent: 21 June 2005 13:29
To: [email protected]
Subject: [bdbxml] asString

 

Hi everyone:

I'm new to DBXML, and having a problem with using the XmlValue.asString
method.  I get a micosoft exception trying do deallocate a pointer from
the heap when I make the call.

I'm using Visual C++ .Net 7.1.  on XP.  Can anyone help?

Nathan
lmpx.com only provides a reader for public news (NNTP) servers. It is not affiliated with the servers or forums shown here and is not responsible for the content of articles, which is written by their respective authors.