Can't import Microsoft Access date field using tAccessInput

[Anonymous]

I am very new to TOS.
I have a very simple table in Access 2003 with several fields. One of the fields is a Date field. This field has no special format. However, when I tried to use tAccessInput to import the data from the table, I received an exception caused by that date field:
xception in component tAccessInput_1
java.sql.SQLException: No data found
at sun.jdbc.odbc.JdbcOdbc.standardError(Unknown Source)
at sun.jdbc.odbc.JdbcOdbc.SQLGetDataStringTimestamp(Unknown Source)
at sun.jdbc.odbc.JdbcOdbcResultSet.getDataStringTimestamp(Unknown Source)
at sun.jdbc.odbc.JdbcOdbcResultSet.getTimestamp(Unknown Source)
at talenddemosjava.testing_0_1.testing.tAccessInput_1Process(testing.java:645)
at talenddemosjava.testing_0_1.testing.runJobInTOS(testing.java:966)
at talenddemosjava.testing_0_1.testing.main(testing.java:860)
I have no idea why this is happening. I tried to change the data type of the date field in the schema and I got something like: 1984-12-05 00:00:00
I tried many date pattern possible such as "yyyy-MM-dd'T'HH:mm:ss". I constantly received the same exception.
Would you please help me to solve this problem?
Thank you very much.
Toan.

[Anonymous]

My TOS is 4.0.0M1

[Anonymous]

Email sent. Did you have it? Please post your reply here. Thank you so much.

[Anonymous]

Hello
I test it on TOS3.2.3 and it works fine.
query:

"select Table1.SalesUnits,Table1.SalesDollar,Table1.SalesCost,Table1.CustID,Table1.StoreID,
Table1.ItemID,Table1.myDate 
from Table1"

Best regards

shong

[Anonymous]

I did exactly what you did and had no luck. Same exception appeared. Is there any chance you can test it on TOS 4.0.0 because it's the version that I can download.

[Anonymous]

The dates displayed on my computer is in "MM/dd/yyyy" format. So I use "MM/dd/yyyy" date pattern in Talend. But I still can't get it to work. Is there any chance this problem is caused by the 64bit operating system that I'm using. Moreover, the "Date pattern" in TOS should only define what date data should look like in TOS only. Is that correct? If I have to define the explicit "date pattern" to match each format of all the date fields from all the data sources, I wonder how many different jobs I have to create to handle just date fields.

[_AnonymousUser]

I am having the same issues in TOS 4.0.0M3. I have several date fields in an Access table, some of which are formatted as "mm/dd/yyyy" and some that are formatted as short time ("hh:mm"). If I leave all the date fields out, my import runs fine. As soon as I include any of the date fields in the import process, it fails with the same error messages shown above. I am using Windows XP, so it not limited to just 64-bit systems.

[_AnonymousUser]

Update: my import runs fine in TOS 3.2. There must be a bug in TOS 4.0 that causes dates in Access to not work.