MPE messes up messages and dates when moving to archieve

[rene]

Hi!

I have had problems when moving my sent mesages from my k800i to the mpe archieve. This are the steps what i'm doing:

1) i add manually to my sent-messages the correct timestamp (check the sent timestamp from the phone, type it into MPE)
2) When i have 20-30 messages, i mark them to be moved to the archieve

Now to the problem

Sometimes MPE warns that there are identical messages in the archieve. Just to be sure that i get all messages moved, i let mpe move the messages again cause ignoring this makes mpe skip the messages, and it could be that the messages might get deleted (TIP: Please add a CANCEL option to this prompt, cause i would like to manually check which messages might be double, and then I could delete these messages either from the phone or MPE).

After such a transfer i browse through my archieve to look for the double-messages. Usually i find them, and i discover that all the doubled messages have the same timestamp (probably they got set during a previous transfer of modified mesages, or because of the double-conflict??)

I have not yet found a way of reproducing this problem, but i guess it has do do with the PartUID or StoradeID.

My phones SMS-memory is closely to full, and i think that this (bug?) has to do with this.

I would like to hunt this issue down, but i think that i would need to be able to see the PartUID and StoradeID for each messages. Are the viewable fields in MPE set in the MPE-code itself, or can these be overridein in a config-file? Is there a way to get these fields viewable (and why not all fields used in the messages)?

[FJ]

I don't think it has to do with StorageIDs, MyPhoneExplorer only compares the PDU on duplicate-check - not the StorageID.

I will try to reproduce it.

[rene]

Ok. Thanks!

What about displaying other data-fields in the MPE-GUI? Is that possible to add a "debug-mode" where these might be visible?

[FJ]

I don't see the sense in displaying StorageIDs. If you know them or not - where is the sense ?

[rene]

I was actually meaning the PartUID field, cause you once explained in a post (http://www.fjsoft.at/forum/viewtopic.php?t=4355) that there are numbers only between 0 and 255.

Isn't this one reason why for example messages are getting mixed up with each other when for example moving two messages that happen to have the same PartUID?

[FJ]

You can read out the PartID for testingpurposes with the Tool PDUSpy. I don't think either that this is the problem. The messages get joined when MPE reads it out from the phone. When moving it into archive one message is a single object, in this case it makes no diffrence if its a single or multiple message - its already joined to one object.