Bartender With Excel / Database Field Type
Greetings,
I've been using BarTender software with Excel spreadsheet successfully for a long time - the initial connection to the XLS file is easy and the program itself detects the database fields types such as DOUBLE, WCHAR automatically. However, I've run into a problem with one row which constantly is detected by BarTender as DOUBLE field type and therefore when I print a label it gives me i.e. 0000 instead OT0000 as in the Excel file. Could you please advise where I can change the field type in order to enable BarTender to correctly recognize entire fields with both letters and numbers?
Thank you!
I've been using BarTender software with Excel spreadsheet successfully for a long time - the initial connection to the XLS file is easy and the program itself detects the database fields types such as DOUBLE, WCHAR automatically. However, I've run into a problem with one row which constantly is detected by BarTender as DOUBLE field type and therefore when I print a label it gives me i.e. 0000 instead OT0000 as in the Excel file. Could you please advise where I can change the field type in order to enable BarTender to correctly recognize entire fields with both letters and numbers?
Thank you!
0
-
It is not possible to specify a field type as the OLEDB/ODBC driver decides on a file type for BarTender based on the first few rows of data in the sheet. Any non-conform data for that field will be dropped and BarTender will not even receive it.
The best workaround is to use a proper database that can specifically set a data type that will be true for all records on that field. Otherwise, have a data record in the first row that will cause it to be recognised as string data and thereby supporting all character data; or to export the sheet as a CSV text file and have BarTender connect to that instead.0 -
Gene Henson
★ BarTender Hero ★
You can look at the document posted [url="http://seagullscientific.invisionzone.com/index.php?/topic/693-missing-data-from-microsoft-excel/"]here[/url] to see another workaround in addition to the ones that Ian already mentioned. Specifically, you can try adding the IMEX=1 property your connection string which might help the situation. 0
Iniciar sesión para dejar un comentario.
Comentarios
2 comentarios