The production of this Excel file is automated from another system. The plan is for the importer to pick this file up from a specific location and then to run automatically on a scheduled basis. This process happens on a customer site every day. My job is
to automate the process which requires no human interaction so opening the spreadsheet and creating a second column and manually formatting that, is NOT an option.
My job is to ensure this has no manual interaction at all.
okay, so you are not adding the import profile to the Excel file; the profile is somewhere else and you needed to look in the XLS file just once to get the layout so you could set the import profile correctly. You didn't need to save the XLS file.
So what I said earlier:
>> So you have to use Excel to open, modify and save the XLS file
>> because you need to set up the import profile for the ODBC connection.
is completely wrong.
In fact, Excel is not used at all! One system is writing a file with an XLS extension in an Excel readable format. A second system is using ODBC connectivity to read the XLS file and import the data.
I suggest you use a simple text editor like Notepad or Wordpad (not Word) to look at the XLS file as it comes from the first system. It might be easier to do this if you make a copy and change the extension
from XLS to TXT to avoid Windows using Excel. Do you see the date/time the way you want it? If there are several columns in Excel you will probably find that the TXT file has TAB characters separating the columns. You can set your ODBC to import from the
text file even though the file extension is misleading.