![]() A non-printing character would be good as it will not alter the displayed value. If one pre/appends a non-numeric and/or non-date character in the value, the value will be recognized as text and not converted. where human-readability might be important.where the file might be imported into a program other than MS Excel (MS Word's Mail Merge function comes to mind),.Two cases that I can think of that the "prepending =" solution, as mentioned previously, might not be ideal is Or the value contains characters that can be confused with mathematical operators (as in dates: /, -). Which sometimes can start with one or more zeroes (0), which get thrown away when converted to numeric. A couple of examples where this is problematic: The problem is not only with dates in text fields, but anything numeric also gets converted from text to numbers. ![]() ![]() CSV files are easy to generate from most programming languages, rather small, human-readable in a crunch with a plain text editor, and ubiquitous. I know this is an old question, but the problem is not going away soon.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |