Convert CSV to XLS: Easy & Fast

Hello, I'm almost too afraid to ask...
"However, after I had already messed up the numbers after the conversion, I read again: Ulf's explanation says to save the CSV file as XLS immediately after opening it. I opened the file, saw all the numbers on the left, and then used the conversion program to put the numbers into columns (replacing the source file), but the headers got mixed up."
Today I tried to log in to my Touran, and after some initial attempts, I got the same result.
What am I doing wrong? I'm going to delete everything and try again.
Did anyone solve this problem right away? Is it related to NT?
What is the correct procedure?
Can someone teach me this? If I understand this, I might be able to make progress with the T5 log as well.
Sure, thanks in advance.

Quote:

What is the correct procedure?

"Alternative: convert the log file to a .xls format using the CSV converter (which can be found in the VAGCOM directory after installation in newer VAGCOM versions as CSVConv.exe), or import the file into Excel and proceed accordingly."
Please provide the text you would like me to translate from German to English. I will then provide the translation without any explanations.


"Personally, I don't use such tools at all, because I don't have any MS Office programs installed on my computer. The results with OpenOffice are either unsatisfactory or too complicated. And I simply don't have the time to constantly transfer the data back and forth between my computer and a machine with Office installed."

That's why I use a CSV viewer that quickly and clearly displays the raw data without any unnecessary frills.

Hi Klaus,

The problem isn't NT, but the language.

Excel takes internationalization to such an extent that a German version of Excel might react completely differently to the same CSV file compared to an English version.

The background information concerns the characters used.

"hundred-thousand-comma-three" in German translates to 100,000.3 or possibly 100,000.3.
english but 100000.3 or 100,000.3

CSV, which stands for "comma-separated values," naturally has a problem with the characters ",", ";", and ".".

Your converter replaced all non-numeric characters with semicolons, so the number above became 100;000;3.

m;

My Excel program can read the original logs from VAGCOM 704.1, but it cannot read the logs converted from CsvConv.

Microsoft products not only require a purchase, but also always necessitate training on how to work around all the quirks and bugs.

m;

teileklaus wrote:

Immediately after opening, I had all the numbers on the left, and then I used the conversion program to get the numbers into columns (by replacing the source file). The headers were then mixed up.

In that case, it can help to open the .csv file directly from Excel (using "File" -> "Open"): Some clumped .csv files appear to me (for some reason) neatly organized with the (log) data in their own columns, as they should be.
Then I'll save this lucky occurrence immediately as a .xls file, and the problem with data aggregation will be solved.

I have updated the invoice accordingly.

Hello everyone,

I'm taking a slightly different approach, but it's worked well so far:

I rename the *.csv and *.txt or *.asc files and then import them directly into Excel.
If you remember to adjust the decimal separators accordingly (see Martin's comment), you can quickly and easily work with Excel data.

Best regards, Jochen.

P.S.
Once all of our requirements have been incorporated into Rainer's KDatascope, hopefully the conversion problem will be completely resolved.

dieselmartin wrote:

Excel takes internationalization to such an extent that a German version of Excel reacts completely differently to the same CSV file than an English version.

Not only that, but the fun is even version-dependent .

ulf wrote:

It can be helpful to open the .csv file directly from Excel (using "File" -> "Open"): Sometimes, these clumped .csv files appear to me (for some reason) neatly organized with the (log) data in their own columns, as it should be.

"Exactly, I've noticed that too."

Hello fellow enthusiasts,

I also experienced the 'number chunking problem.'
I fiddled around for at least an hour, and lo and behold: still a jumble of numbers!
Es wird z.B. das Tastverhältnis 24.7% in 24. July translates!!

While reading the FAQ about 'Creating and preparing log files with VAGCOM for the forum,' I came across a small paragraph that mentioned a '.csv converter in VAGCOM.'

This converter works well (although there are often a few strange characters at the end of the file, but otherwise it's fine).

Normally, more intelligence comes *out* of a computer than goes *into* it , but here, (finally) it's the opposite........

Best regards, Kassen.

Hello!

It's much simpler than that.


Create a new Excel file.
Then, go to 'Import Data'.
Then, select the original VAG-COM file (.csv).
-> A box opens -> go to 'Separate' and then click 'Next'.
-> new field -> select comma instead of tab, then continue.
-> new sheet -> now select EVERY column and change the format to TEXT (otherwise, Excel will change '1.24' to 'Jan 24', which is very bad!). Then proceed.
-> Then finish it and that's it!

Best regards,