🚀 go-pugleaf

RetroBBS NetNews Server

Inspired by RockSolid Light RIP Retro Guy

Article View: borland.public.cppbuilder.internet.web
Article #1348

Re: Problems using TXMLDocument

#1348
From: Carlos Botto
Date: Wed, 23 Feb 2005 21:46
70 lines
3016 bytes
Remy,

Thank for your answer.
Yes this is the whole error message. The error window title is "Application
error".
I still have the error.

I had another problem linking the DLL, I got some "unresolved external"
errors:
[Linker Error] Unresolved external '__fastcall
Xmldoc::TXMLDocument::LoadFromFile(const System::WideString)' referenced
from Z:\GRAPH ENVIRONMENT\OBJECT\CHILD.OBJ

[Linker Error] Unresolved external '__fastcall
Xmldoc::TXMLDocument::GetDocumentElement()' referenced from Z:\GRAPH
ENVIRONMENT\OBJECT\CHILD.OBJ

[Linker Error] Unresolved external 'Xmldoc::TXMLDocument::' referenced from
Z:\GRAPH ENVIRONMENT\OBJECT\CHILD.OBJ

But I saw in another post that the solution for that was checking "Build
with runtime packages" in Options. Is that correct?

I have the feeling that both problems are related.

Thanks again



Carlos

"Remy Lebeau (TeamB)" <no.spam@no.spam.com> wrote in message
news:421ce683@newsgroups.borland.com...
>
> "Carlos Botto" <carlosb@qualitau.com> wrote in message
> news:421ce3f0$1@newsgroups.borland.com...
>
> > The error message is : "Exception EOleException in module
> > xmlrtl60.bpl at 00082831"
>
> Is that the whole message?  There should have been a text message included
> that described the reason for the error.
>
> >  XMLDocument = new TXMLDocument("");
>
> Do not use TXMLDocument dynamically like that.  TXMLDocument works
> differently when instantiated dynamically.  Use the IXMLDocument interface
> via NewXMLDocument() and LoadXMLDocument() instead, ie:
>
>     void TChildFRM::ReadXMLFile(AnsiString FileName, XMLFileDescription
> *FileDesc[])
>     {
>         _di_IXMLDocument XMLDocument;
>         //...
>         if( FileExists(FileName) )
>         {
>             XMLDocument = LoadXMLDocument(FileName);
>             //...
>         }
>         else
>         {
>             XMLDocument = NewXMLDocument();
>             //...
>         }
>     }
>
>
> Gambit
>
>
Technical Details
Message-ID: <421cf9a4$1@newsgroups.borland.com>
Path: arc1-ca.pugleaf.net!g2news1.google.com!news1.google.com!newsread.com!newsprint.newsread.com!38.119.100.83.MISMATCH!news-out.nntp.be!propagator2-sterling.newsfeeds.com!news-in.newsfeeds.com!in.nntp.be!caladan.landsraad.net!newsgroups.borland.com!not-for-mail
References: <421ce3f0$1@newsgroups.borland.com> <421ce683@newsgroups.borland.com>

Show Full Headers
Complete Article Headers
X-Google-Thread: feeec,4a54551f5d9bd767
X-Google-Attributes: gidfeeec,public
X-Google-Language: ENGLISH,ASCII-7-bit
Reply-To: "Carlos Botto" <carlosb@qualitau.com>
From: "Carlos Botto" <carlosb@qualitau.com>
Newsgroups: borland.public.cppbuilder.internet.web
References: <421ce3f0$1@newsgroups.borland.com> <421ce683@newsgroups.borland.com>
Subject: Re: Problems using TXMLDocument 
Date: Wed, 23 Feb 2005 13:46:11 -0800
Lines: 72
X-Priority: 3
X-MSMail-Priority: Normal
X-Newsreader: Microsoft Outlook Express 6.00.2800.1409
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1409
NNTP-Posting-Host: 64.2.27.194
Message-ID: <421cf9a4$1@newsgroups.borland.com>
X-Trace: newsgroups.borland.com 1109195172 64.2.27.194 (23 Feb 2005 13:46:12 -0800)
Path: arc1-ca.pugleaf.net!g2news1.google.com!news1.google.com!newsread.com!newsprint.newsread.com!38.119.100.83.MISMATCH!news-out.nntp.be!propagator2-sterling.newsfeeds.com!news-in.newsfeeds.com!in.nntp.be!caladan.landsraad.net!newsgroups.borland.com!not-for-mail