We have an application which is outputting csv files where the dates are shown as "dd/mm/yy" with no leading zeros. So the 1st March 2001 would appear as "1/3/01". It also may output long database fields of >256 chars and containing hard returns and other special characters.
Excel is the registered application for csv files and opens them automatically. Excel handles the dates fine on some clients (UK, W2000/XL2000 and W95/XL97) but not on others (in France and Spain W95/XL97). It also handles the long text with no issues. The problem with the dates is that XL seems to be trying to bring the data in as mm/dd/yy and so some of the dates are incorrect and the rest are left as text because the are interpreted as invalid eg 25/1/01.
If we use manual import to open the files we can cure the date format but it does not parse the long fields correctly.
I thought it might be to do with regional settings (XL seems takes its default date display format from there) but the format in all three locations is dd/mm/yyyy HH:mm.
Can anyone suggest any other places in the client configuration that might control the import format used for opening csv's.
Excel is the registered application for csv files and opens them automatically. Excel handles the dates fine on some clients (UK, W2000/XL2000 and W95/XL97) but not on others (in France and Spain W95/XL97). It also handles the long text with no issues. The problem with the dates is that XL seems to be trying to bring the data in as mm/dd/yy and so some of the dates are incorrect and the rest are left as text because the are interpreted as invalid eg 25/1/01.
If we use manual import to open the files we can cure the date format but it does not parse the long fields correctly.
I thought it might be to do with regional settings (XL seems takes its default date display format from there) but the format in all three locations is dd/mm/yyyy HH:mm.
Can anyone suggest any other places in the client configuration that might control the import format used for opening csv's.