Export file in wrong format -> U8-DOS - ExportZen: Feedback Forum - ROXORITY ™ Sensational SharePoint Solutions
User Voices
(Loading...)

ExportZen: Feedback Forum > Export file in wrong format -> U8-DOS

One of my colleagues uses the tool often and sees that the exported csv file (through the commandline) is of the format "U8-DOS". In this format he is unable to import the file in a SQL database. He says that importing the file will be possible when it is in the format "UTF-8" or "ANSI".

Is it possible to change the exported format to something other than U8-DOS?

regards,
Marc

May 6, 2010 at 20:31 | Unregistered CommenterMarc Molenaar

Hi Marc,

we always used UTF-8. The only thing we changed recently (to support your Dutch special characters) was prepending a certain byte-order mark (BOM) so Excel (and potentially other software) can show all non-ASCII characters correctly.

So the question is what other tools or custom your colleague is using and what SQL product this should get imported to. Some tools let you specify the encoding to use during import. Is this custom code or only 3rd-party software, and which?

May 7, 2010 at 0:17 | Registered CommenterROXORITY

My colleague says that he uses the command bulk insert (part of MS SQL 2005 server) to import the csv file.

May 11, 2010 at 20:16 | Unregistered CommenterMarc Molenaar

does Roxority have a tool to convert UTF-8 documents to 'normal' dos documents ? The UTF-8 documents are currently not read by the 'bulk insert' command of SQL server. Within Notepad is an option to do a 'save as' and change the encoding to ANSI which works OK, however there is no way to automate this..
So the best solution would be the "ANSI" option in Roxority ......

May 31, 2010 at 15:43 | Unregistered CommenterRob van OSnabrugge

We will add that option. Notice that we formerly changed this to another encoding for SBM in order for this to read in correctly into Excel, so if you later change that yourself back to 'SQL/DOS encoding' the same export might again look odd in Excel -- you might have to define two exports on the same data then, one for Excel and one for SQL if the same export is to be used in both.

I will send you an email as soon as that option becomes available.

May 31, 2010 at 18:51 | Registered CommenterROXORITY