![]() |
![]() | ![]() | ![]() | Altova Mailing List Archives>Archive Index >microsoft.public.xml Archive Home >Recent entries >Thread Prev - XML Document becomes corrupt after moving 9335 nodes >Thread Next - Re: XML Document becomes corrupt after moving 9335 nodes Re: XML Document becomes corrupt after moving 9335 nodesTo: NULL Date: 11/3/2006 10:00:00 AM There definitely is no maximum number of nodes for the document that you are hitting in this scenario....10,000 nodes is not alot of nodes for some types of data. When you say the program crashes, what do you mean exactly? Can you reproduce it with a debugger attached? "David Webb" <strangecargo> wrote in message news:%23rkPVoq$GHA.4604@T...... >I have a VB.Net application that is trying to organize a very large xml >file > that contains 52,000 nodes. The process starts by creating an XML document > that has a root node and 52k child nodes. The code then organizes the > nodes > based upon data from a database table. The process works fine up until it > reaches the 9336th node at which time the XML Document object no longer > has > any properties and the program crashes. > > Is there a maximum number of nodes for an XML Document or is there another > problem? > > David > > | ![]() | ![]() | ![]() |
| Company | Legal | Press | Partners | Careers | Sitemap | Contact Us | Altova Blog | |||||
|
