FJ Software

I exported my text messages by month because the system would not do my thousands of text messages at one time.

I went to import them and I am getting an error message on a bunch of months with the error message saying the selected file contains no messages. When I look at the file size, there is something there.

I no longer have the old text messages or that phone, so I need to find a way to restore what I exported.

Try to import the file into the SMS archive, does that work?

Please allow me to step in here: do not want to start a new thread about the same thing.

Facing the same thing. Repeatedly tried to download all.

In MyPhoneExplorer on Windows, select "Conversations" in the tree (left)
then at the top, download all.
A pop-up shows up "Please wait... load messages from phone... Importing data"

The "Archive (computer)" remains empty and nothing new is showing up/saved on my PC.

Then I tried following: select 1 sender, select all text messages from that sender. Download.
Same results as above, download, pop-up, etc.

Then I tried to select same sender, select all, copy to Archive.
the entries are then copied into Archive (nothing on PC)
From Archive select all, button "download entire", nothing.

Tried a few times, gave up.

Could be that I am doing something wrong?

MyPhoneExplorer v2.1
Windows 10 x64-PC

Thanks.

--
LATER:

Workaround :
select/expand all senders, then select all textmessages, r-click Export/Import > Export Selected Messages (they are saved to .csv)
when loaded into Excel there were 11 errors

I loaded them into Excel and they looked like this:

[/img]

Maybe the export is not successful because of the errors?

Obviously, something goes wrong in the export - import procedure, but I cannot see which step. When you look at the screenshot, you see that the column data does not match the header. This is usually due to wrong import options in excel or similar programs, because the CSV format is no unique standard CSV, see here:
https://en.wikipedia.org/wiki/Comma-separated_values
It might be helpful, to post a part of the file in text format to locate the problem.
For yourself, you could view the file using a text editor such as windows notepad.
When importing the CSV file to a spreadsheet, you must configure the correct field separator and delimiters: The field separator is ; and the non-blank values are enclosed in "" as delimiters.
The delimiters allows the field separator to be part of the value. Such garbling happens, if field separator and delimiter definition of the exporting program does not match definition of the importing program or if one of the program does not handle the situation where separator and/or delimiter are part of the value (here: the message text).
First, try an excel import with adjusted separator and delimiter settings.
If that does not produce valid contents in every line, check the separator and delimiter rules using a text editor and adjust the contents where necessary.
Best is the delimiter character " not appearing anywehre but as delimiter, that means: not in the text message - replace by ' oder something similar. Same for the separator character ; which should not appear in the text messages, otherwise remove or replace. Remember to backup modified files to preserve the original.

Furthermore, Excel tries to guess the data type from the read values, which does sometimes lead to unwanted results. All fields should be treated as text.

I already found out.
Pasted the text into an editor and made invisible characters visible.

There is a line feed (not carriage return line feed, CRLF), but just a LF on that place, that should -not- be there.

so it is textextextLF";"text
where is should be: textext";"text text

(the ; being the field separator)

Manually corrected this. There were just a few, 11 I believe.
Import into Excel went fine.

mpwul62 hat geschrieben:There is a line feed (not carriage return line feed, CRLF), but just a LF on that place, that should -not- be there.

Thank you for the feedback. In general, CSV should be capable to process control characters in the fiel values, however you might have read in the above mentioned wikipedia article:

many CSV implementations do not support embedded line breaks

Furthermore, there is no general rule, whether LF, CR or CRLF indicate line separation. Good to know.