Please, reformat your code to use proper, consistent indenting. That will make it much easier to spot the issue you are running into.

I really don’t get the logic of starting to write an XML file while trying to read that same file. How is that supposed to work?

first i read the file to see if there is a patient with the same id. if there isn’t a patient with that id i write to the file the examinations for that patient.

i don’t understand how to make my code

I mean a formatting like below, makes your code more readable and thus makes it easier to spot what is going wrong.

I don’t think it is a good idea to try to write to a file from the function that is supposed to read from it. IMHO, it is better to separate that into different functions, and don’t call the one from the other.

In that way i had done the format of the code.

ok, i will seperate the two functions but you didnt response to my problem.

The problem is that it gets in the while loop only once and the value of the id2 is always the same.
it doesnt read the next patient_id

annatz wrote:

In that way i had done the format of the code.

ok, i will seperate the two functions but you didnt response to my problem.

The problem is that it gets in the while loop only once and the value of the id2 is always the same.
it doesnt read the next patient_id

Could you post the XML that you are trying to read then? We can not check if the code is at fault in this case.

i write the xml but at the preview it is different.

the number 1 that is after examinations is after patient_id. and after examinations is the tag patient_exams

Edit: reformatted XML to make it more readable. Please do that yourself next time; Andre

With the above piece of XML, and the code that you showed, you will encounter the patient_id tag twice: once for the openening, and once for the closing tag. id2 will contain the text “1” on the first call, and be empty for the second (read the docs on readElementText for an explanation why).

It is obviously always the same, because the XML does not change all of a sudden during the reading (that is: you should not change the XML, as I told you before).

Have you considered using QDomDocument [doc.qt.nokia.com] instead?

This will create an in-memory representation of your XML document which allows for searching and inserting / removing nodes.

Yes, but QDomDocument is considdered EOL and is thus not wise to use in new code.

I change my code like this:

but now the program craches.

Again: please make your code easy to read here. Take care of indentation and the likes.

Then, your code looks like nonsense. First you iterate through the whole XML in search of a StartDocument tag, and then you do nothing with it. Then, you expect there is more to read?
A crash is easy to debug usually. Your debugger will tell what line triggered the crash.

Andre wrote:

Yes, but QDomDocument is considdered EOL and is thus not wise to use in new code.

It is? It is not listed as deprecated in the documentation and the module maturiy list [labs.qt.nokia.com] also states it as done (not deprecated). Is there another source to look at when evaluating module lifetime?

XML DOM should never be EOL. It is the only means to manipulate an XML document in-memory. And sometimes there are cases where you just plain cannot use a stream writer, e.g. when you need to add nodes at two different places in the tree simultaneously.

Let me put it this way: if I am wrong, then Thiago was wrong. He’s the one saying something along these lines, but I can not remember if it was on IRC or on the mailinglist.

Maybe it’s EOL in the sense of “no new features”. But there’s far too much code out there that relies on QDom. One should consider the stream classes for new projects, though.