x Want to participate? Join the group to interact
Options
  • Replies 6 replies
  • Subscribers 105 subscribers
  • Views 6647 views
  • Users 0 members are here
Browse Forums
Announcements
293
topics
370
replies
Business Object Interface
1k
topics
7k
replies
Core Financial Modules
2k
topics
8k
replies
Customization and Productivity
3k
topics
12k
replies
Distribution, Manufacturing, and Applications
2k
topics
7k
replies
General Discussion
1k
topics
3k
replies
Partner Cloud
44
topics
90
replies
Payroll, Time Tracking, and Job Cost
776
topics
1k
replies
Reporting and Analytics
960
topics
3k
replies
Sage CRM for Sage 100
164
topics
357
replies
Technical and Installation
2k
topics
9k
replies
Year-end Forum
89
topics
237
replies
Oren Levy

ODBC & SQL import issues

Posted By

Hi Everyone.

 

I'm running into a brick wall with MAS200 4.4 and SQL.

We are currently running MAS200 4.05 and importing data from it via ODBC into SQL 2000 and SQL 2005 for our e-commerce web site and data warehouse for reports (using DTS in SQL 2000 and SSIS in SQl 2005).

 

We are testing the 4.4 environment and we can't seem to be able to import anything into SQL.  MSACCESS and Excel are working fine but seems like it has some issues with SQL.

 

In SQL 2000 I'm getting the following error when trying to import the data:

 

Error Source: Microsoft OLE DB Provider for ODBC Drivers

Error Description: [providex] [ODBC Driver] Unexpected extra token:

Context: Error Calling OpenRowset on the provider.

 

SQL 2000 ODBC Error

 

In SQL 2005 I'm not even getting the list of tables.

 

Any ideas anyone????

 

Thanks

 

Oren

  • Were you able to resolve this issue?

     

    I find myself with the exact same problem.

  • I found a solution.

     

    On the Transform Data Task Properties of the SQL 2000 DTS:

     

    Instead of selecting the Source Table use a SQL query to build the selection.  i.e. select * from IM_Item

     

     

    In v 4.3 the DTS task would see the table as IM_Item in the dropdown.  In v 4.4 the DTS sees the table as "IM.Item"."IM.Item".  I believe the decimal and everything after is throwing the "unexpected extra token" error.

  • I believe you want "SELECT * FROM CI_ITEM" not IM_Item.

     

    Dawn

  • Oops...You are correct...Typo. 

     

    I guess that is what happens when you spend all weekend working on an upgrade!

     

  • Yes.

     

    Thsi is what I did.

     

    On the Transform Data Task Properties of the SQL 2000 DTS:

     

    Instead of selecting the Source Table use a SQL query to build the selection.  i.e. select * from CI_Item

     

    Let me know if you need further clarification. 

  • How so?

     

    The problem only arises if you are selecting the entire table using the dropdown for the table source.  If you are selecting the entire table anyway is it any better/worse then using a SQL statement to establish your source table?

     

     

*Community Hub is the new name for Sage City