Re: XMLDocument - Eeek

•

What is DaniWeb IT Discussion Community?

You're currently browsing the Pascal and Delphi section within the Software Development category of DaniWeb, a massive community of 397,836 software developers, web developers, Internet marketers, and tech gurus who are all enthusiastic about making contacts, networking, and learning from each other. In fact, there are 2,559 IT professionals currently interacting right now! Registration is free, only takes a minute and lets you enjoy all of the interactive features of the site.

Join our community!

Please support our Pascal and Delphi advertiser:

XMLDocument - Eeek

•

Join Date: Jul 2006

Location: Deptford, London

Posts: 943

Reputation: MattEvans has a spectacular aura about

Rep Power: 5

Solved Threads: 47

MattEvans

Online

Posting Shark

Re: XMLDocument - Eeek

Jul 20th, 2006

The solution was to put an instance of the XMLDocument object on my form at design time.. Not perfect because I have to reuse it for an exponential number of XML documents, and now I have to think carefully about forking/threads.

I can't understand the problem in my code, if it wasn't working atall that would make more sense, but sortof working is much more confusing. I'm gonna check the properties of the standard dropped-on-form XMLDocument and a runtime constructed XMLDocument later, for now though I'm hoping I have the order of operations right to avoid instance corruption.

Has anyone else experienced similar outcomes when using XMLDocument components created at runtime?

Forum Highlights

Related Features

DANIWEB FEATURE INDEX

Statistics

Members: 397,836

Users Online Now: 2,559

Active IRC Users: 24

Forum Threads: 129,492

Forum Posts: 664,253

Code Snippets: 883

Blogs: 146

Blog Entries: 2,110

Directory Links: 567

DaniWeb Home > Forums > Software Development > Pascal and Delphi > XMLDocument - Eeek

Re: XMLDocument - Eeek

XMLDocument - Eeek

Re: XMLDocument - Eeek