Marty O
Member
Hi All,
I am currently developing an app that will need to import data from E1(8.11) Tools R(8.97) DB2 into MSSQL 2005.
The first problem, I am forced to use ODA. There are no alternatives at the moment.
What I want to do:
1. Create a linked server in MSSQL ==> done
2. Create stored procedures to extract data ==> done
3. Solve a problem as follows:
When I actually do run a query against the linked server, all works except for any tables that contain date fields. The problem (it would seem after testing with Visual Studio) is that all date fields within a table get their field name changed at random to something else like 00020 instead of ADUPMJ, thus resulting in an error in MSSQL stating that the field does not exist.
Interesting enough, in Crystal Reports 2008, no such problem.
What I have:
1. Windows 7 Pro 64 bit
2. JDE Fat Client (developper components installed)
3. ODA drivers, config, login, etc ...
4. MSSQL 2005 Latest SP
5. Visual Studio 2008 and 2010.
Has anyone encountered this before ? or has anyone have insight of what extra config I need for this ODA nightmare ?
Thanks
I am currently developing an app that will need to import data from E1(8.11) Tools R(8.97) DB2 into MSSQL 2005.
The first problem, I am forced to use ODA. There are no alternatives at the moment.
What I want to do:
1. Create a linked server in MSSQL ==> done
2. Create stored procedures to extract data ==> done
3. Solve a problem as follows:
When I actually do run a query against the linked server, all works except for any tables that contain date fields. The problem (it would seem after testing with Visual Studio) is that all date fields within a table get their field name changed at random to something else like 00020 instead of ADUPMJ, thus resulting in an error in MSSQL stating that the field does not exist.
Interesting enough, in Crystal Reports 2008, no such problem.
What I have:
1. Windows 7 Pro 64 bit
2. JDE Fat Client (developper components installed)
3. ODA drivers, config, login, etc ...
4. MSSQL 2005 Latest SP
5. Visual Studio 2008 and 2010.
Has anyone encountered this before ? or has anyone have insight of what extra config I need for this ODA nightmare ?
Thanks