On Tue, 3 Sep 2019 10:12:54 -0700, Tom Brennan wrote: >And be careful even with the quotes. For example, if I use a script to >create a csv file containing something like this: > >"3390","12E3" > >On my Win 10 system, even with the quotes that unit address turns into a >number because Excel apparently thinks it's an exponent representation. > Ouch! So it improperly strips the quotes before attempting to categorize the datum!
(I've had similar problems with Word under Exchange attempting to treat "BLKSIZE=6100" as quoted-printable, "BLKSIZEa00"!) >I can fix that by putting an "=" in front such as: > >"3390",="12E3" > >Often I'll script everything as ="data" because I don't want Excel to be >messing with any field. > Ouch! The metric is to minimize phone calls to Tech Support, even counting user errors. -- gil ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to [email protected] with the message: INFO IBM-MAIN
