Can somebody help me with this problem?
We are receiving XML files with some data, but then I open that XML file using Excel values are not the same like when I use notepad to open same XML file.
For example
This is what is diplayed when I open using Excel
And when i open it using Notepad in the same place value is different
as you can see, values are different in last digit.
Excel reads it as "0" for last digit, but in Notepad last digit is "1".
Does somebody knows a reason why this is happening?
Since there is no response over here, i am putting link from microsoft community where i also started a dispute and there are some replays (not exactly solutions) but explanation why this scenario is happening
https://answers.microsoft.com/en-us/msoffice/forum/all/opening-xml-using-excel-values-wrongly-imported/87b69b13-bbd4-4c02-9776-b2644084935b?page=2
Related
I recently created an automated Excel utility (using Microsoft Office 2019), in which I've extensively used data validations, VBA code, named ranges and formatting. It was working well until one day I received an Excel prompt message that read:
When I click on Yes, it gives me another pop-up where it says it recovered the file, and also gives me a link to the error log XML file. I click on it and open the .xml file using my default browser, and it shows the following details:
Looks like it is removing data validations from a particular sheet, and I realize that is true when I navigate to that sheet in the UI. To work around this unwarranted and repeated data-validation removal that Excel application is enforcing, I created a macro code that will re-instate all these data validations as required. The real problem arises when this Excel file is opened on a different computer with Microsoft Office 365. Looks like it is removing not just data-validations but also other components like named ranges and buttons. There could be other things that it might be removing, which I am unaware of at the moment. So the macro created to re-instate the data-validations is no longer useful.
Why does this problem arise? And why is different version of Excel behaving differently? How do I solve this? Appreciate your kind help. Thank you!
As rightly suggested by Ron Rosenfeld and e_conomics, the issue was with the data validation lists, whose sources were strings of comma separated values that were going beyond 255 characters. Apparently, that is a limitation with Excel.
When I replaced the sources of data validation lists (string of comma separated values) with the ranges containing the corresponding values, the problem resolved itself. The repair dialogue never appeared again.
I am using Excel VBA 2016. I have applied all available updates.
This works fine for me when I attempt to insert into a WORD document.
Range.InsertFile FileName:="c:\tmp\filename.rtf"
If I do this...
variable = "c:\tmp\filename.rtf"
Range.InsertFile FileName:=variable
It does not work. The error message is, "Sorry, we couldn't find your file. Was it moved, renamed, or deleted?" Then it gives me the path in parenthesis.
I have unsuccessfully tried all sorts of permutations that might make this work and Googled for too long. Any ideas?
This appears to be a bug in VBA. I was trying to read a list of RTF file names in a Word document I had generated from a different program. Then I was going to insert the RTF back into the same Word document in a new table. I tried both an array and an ArrayList. Both failed. Ultimately, I had to dump these file names into a text file and read it from there. That worked perfectly. Thanks Ahmed for making me do the hard word I was avoiding. Hopefully this helps someone else.
I used python to write some text to csv but it is stored in funny format.
output data is saved here:example data
for example, it is read as the below in csv excel
text shown in CSV
when i copy it to other platforms(notepad, word, web application) it turns into something else
after copy
I tried a numerous method include formatting with the CSV but it just wont work.
Could someone please help me.
With thanks,
Iverson
It's hard to guess what you mean...
Your file has TABs between many characters. But every line starts and ends in a double quote ("). So the whole line is one value (cell).
i am exporting data from database to file, which can Excel read and save.
(CSV) I generate csv, with default format (according to RFC 4180, comma delimeter). As expected, stupid excel read all data and place it to one cell.
(CSV with semicolon delimeter), this one excel read fine, but after change some value and press save (CTRL+S), stupid excel saved it to unreadable file (well done!). No delimeters, no string separators. Ok, so i tried to save it as (CSV format with SEMICOLON delimeter), saved file looks ok, but after opening it with excel, error message was showed - INCORRECT FORMAT - no cell found :D really?!
Generating .xsl file in php. It take too much RAM (about 2GB), so it cant be used.
Do you know any good format, which can excel easily open and easily save?
Thanks a lot!
This question is off-topic, but IMHO Excel 2002/2003 XML Format would be the best choice in your circumstances.
The reason for this is that the data in this format is typed - so you will not see numbers misinterpreted as dates, or phone numbers with leading zeros stripped. I am not aware of the kind of problems you describe, so I cannot say for sure how those will be affected.
I am generating CSV files. My first row it is column names, and it looks like
User ID;First Name;Last Name;Email;...
But if I will change User ID to ID, MS office cannot open this CSV and shows me error
Cannot read record(number of record)
But this file opens correctly on, Notepad++. I am using Excel 2013. Any ideas what is wrong?
You can solve the problem by inserting the following simple text at the beginning (the first line) of your .csv file:
sep=;
This will not be seen when the file is opened in Excel. What it will do - it will explicitly tell Excel that the delimiter is ;, and values will be separated into separate cells. Also, you will be able to use ID as the title of a column. Unfortunately, I cannot answer why Excel does not like it when you use this title at the beginning of the file.