topic Re: Export from Access / Encoding issue in Talend Studio

Export from Access / Encoding issue

Anonymous — Mon, 09 Sep 2013 12:09:12 GMT

Hello
I'm using TOS 5.3.1 ( I also tried with 5.1.1 for the same results).
I have to work with data containing Cyrillic characters.
I use Access 2003
When I try tlogrow I'v got ??? instead of cyrillic character (capture1)
I tried different character setting as UTF-8 (capture 2) but I still have this problem.

Do you have any suggestion ?

Re: Export from Access / Encoding issue

Anonymous — Mon, 09 Sep 2013 12:31:03 GMT

Hi,

When I try tlogrow I'v got ??? instead of cyrillic character (capture1)
I tried different character setting as UTF-8 (capture 2) but I still have this problem.

Did you try this solution
On the Window menu, click Preferences followed by Talend and then Specific Settings. Select the Allow specific characters(UTF8...) for columns of schema box .
Click OK button to save the change and close the window.
Is it Ok with output(delimited file...).
Best regards
Sabrina

Re: Export from Access / Encoding issue

Anonymous — Mon, 09 Sep 2013 12:59:04 GMT

Thank you for your suggestions Sabrina,
But they don't work.
It tried few things
Access 2003 -> TLogRow = ??? (instead of Cyrillic characters)
Access 2007 -> TLogRow = ???
Access 2003 Export to Excel 2003 -> TLogRow = ???
Access 2003 Export to Excel 2007 -> TLogrow = OK I've got the Cyrillic characters

Re: Export from Access / Encoding issue

Anonymous — Tue, 10 Sep 2013 04:47:47 GMT

Hi,

Access 2003 Export to Excel 2007 -> TLogrow = OK I've got the Cyrillic characters

Is it working for Cyrillic characters? Could you post the successful workflow screenshot into forum. tAccessinput-->tFileOutPutexcel-->tlogrow?
Best regards
Sabrina

Re: Export from Access / Encoding issue

Anonymous — Wed, 11 Sep 2013 06:41:36 GMT

If I export data from Access to Excel (as export a table) then I use Talend TLogRow with the excel file it works;
If I try to do everything with Talend, it does not work

Re: Export from Access / Encoding issue

Anonymous — Wed, 11 Sep 2013 09:11:01 GMT

Hi Herve,

If Access 2007 -> TLogRow return ??? (instead of Cyrillic characters) and is not ok
and if Access 2003 Export to Excel 2007 -> TLogrow is fine for Cyrillic characters,
I would suggest that the issue is with the Access driver used by the component and that tLogRow works fine with the encoding.
But if you also tested to set the charSet properties in the advanced option of tAccessInput, I don't see any other option.
How can we know which encoding is used in an Access database ?
Cheers.
Francois

Re: Export from Access / Encoding issue

Anonymous — Wed, 18 Sep 2013 08:38:24 GMT

Hello
I finally found how to solve it by exporting the Access tables in XML then work with XML files.
I used a vb script to do it and it's OK
dim accessApp
set accessApp = CreateObject("Access.Application")
accessApp.OpenCurrentDataBase("C:\mydatabase.mdb")
accessApp.ExportXml acExportTable, "mytable", _
"C:\mytable.xml"
set accessApp = nothing

Re: Export from Access / Encoding issue

JimmyM — Mon, 04 Nov 2013 19:06:52 GMT

Hello
I finally found how to solve it by exporting the Access tables in XML then work with XML files.
I used a vb script to do it and it's OK
dim accessApp
set accessApp = CreateObject("Access.Application")
accessApp.OpenCurrentDataBase("C:\mydatabase.mdb")
accessApp.ExportXml acExportTable, "mytable", _
"C:\mytable.xml"
set accessApp = nothing

So Talend can't read UTF-8 characters for Access?

Re: Export from Access / Encoding issue

Anonymous — Wed, 05 Mar 2014 06:48:07 GMT

Hi,
Here is a unresolved jira issue https://jira.talendforge.org/browse/TDI-28224, please vote for it.
Best regards
Sabrina

Re: Export from Access / Encoding issue

JimmyM — Wed, 05 Mar 2014 13:27:21 GMT

Hi,
Here is a unresolved jira issue https://jira.talendforge.org/browse/TDI-28224, please vote for it.
Best regards
Sabrina

It doesn't seem to want to let me vote for it. It's my ticket I submitted. STILL UNRESOLVED. One possible resolution was to install t Access for the language I need. Laughable. Talend has a problem.
My company actually PAYS for licenses to have access to first tier support. I'm going to ask them to question that approach.