![]() | |
![]() |
| | Thread Tools | Search this Thread | Display Modes |
#1
| |||
| |||
|
#2
| |||
| |||
|
|
Hello! I did search for this one quite a while, but I cannot seem it mentioned anywhere, so let me ask here if someone saw this problem before. The behaviour is confirmed (for me) with Framework Version 1.1 (with all patches for the version applied) I read and write data for an XML file into a dataset, the file is around 13 MB, and contains one table with around 1000 entries (rows) with maybe 12-15 fields, the fields are sometimes a bit longer with maybe 1000 chars. Sounds not to complicated as a structure. Well, what happens on ds.WriteXML is that the writing just cuts off somewhere. No exception thrown, nothing, program flow continues as if nothing had happened. It looks something like this: table field1>This is the text for field1</field1 field2>This is the tex And that is it. The writing stops right within one tag. You only notice the error next time you want to read the file again. It happens only very very seldom, maybe once in 100 writes. It is also not bound to a specific row or data content, it just happens somewhere on the way. Sadly, I have not been able to reproduce it myself, I only know by clients' complaints. So I cannot say how the dataset looks in memory after the error occured, if it is still valid or corrupt after the point the writing stopped. It looks as if the last buffer has not been flushed out of memory into the file. I did make sure it is on a media that is not removeable, sufficient disk space is there, the file written to has time to get closed in orderly fashion... Anyone ever seen that? |
![]() |
| Thread Tools | Search this Thread |
| Display Modes | |
| |