Member Login

Username
Password
Forget Password
New Sign Up
Search Forum

Buy Support
Incidents

If you can't find your answer in the FREE PUBLIC QDeveloper Forum, require URGENT Priority Support, or you need to send us private or confidential information:

Click Here
If you can't login and post questions or you are having trouble viewing forum posts:
 Click Here
Callback
Support

If you live in USA, UK, Canada, Australia or New Zealand, you can leave us details on your question and request us to call you back and discuss them with you personally  (charges apply).

Click Here
 
Buy Support
Incidents
If you can't find your answer in the FREE PUBLIC QDeveloper Forum, require URGENT Priority Support, or you need to send us private or confidential information:
Click Here

Forum : memo fields in SSIS output type errorSearch Forum

Forum Home > QODBC - ODBC Driver for QuickBooks > QODBC v8 Forum

 New Topic 
 
 Post Reply 
[1]  
 memo fields in SSIS output type error 
 Author   Message 
  Katherine 
  
 Group: Members 
 Posts: 3 
 Joined: 2008-09-06 
 Profile
 Posted : 2008-09-06 01:28:41

I am trying to pull in Quickbooks data using an SSIS package in SQL Server 2005.  I am having trouble with all the fields that are greater than 4000 characters, as a test I have tried this in the DataReader Source SQL command:

SELECT {fn convert(Memo,SQL_VARCHAR)} as "memostring" from PurchaseOrderLine

This got me past other errors I was receiving but I still get:

"The output column "memostring" had an invalid datatype value (0) set"

yet on the Input and output properties tab I cannot change the datatypes there without getting an error saying the datatype on the output columns cannot be changed.

Right now I have everything installed locally on my computer (Quickbooks, QODBC).  Can anyone help?

 

  Top 
  Tom 
  6c3c1_sdk-qodbc.gif
 Group: Administrator 
 Posts: 5510 
 Joined: 2006-02-17 
 Profile
 Posted : 2008-09-06 09:16:53
See: Memo 4095 length too long for ODBC query to SQL Server 2005  

  Top 
  Katherine 
  
 Group: Members 
 Posts: 3 
 Joined: 2008-09-06 
 Profile
 Posted : 2008-09-10 23:29:08

I have tried this setting by creating a brand new ODBC connection and a brand new SSIS project and adding this connection and am still getting this same message about the length?

 

  Top 
  Tom 
  6c3c1_sdk-qodbc.gif
 Group: Administrator 
 Posts: 5510 
 Joined: 2006-02-17 
 Profile
 Posted : 2008-09-11 22:56:13

Sorry I missed the fact the error is actually saying it doesn't like nulls. Try:

SELECT {fn convert(Memo,SQL_VARCHAR)} as "memostring" from PurchaseOrderLine where Memo is not null

 

  Top 
  Katherine 
  
 Group: Members 
 Posts: 3 
 Joined: 2008-09-06 
 Profile
 Posted : 2008-09-11 23:15:43
This is still not working.  I have convert fields checked and limit length set to 3992.  I created a new SSIS project and added a data source (ADO.NET data source) for this connection.  I add a data flow task and then a datareader source and select the connection, enter the SQL and get the error that the output column 'memostring' has a length that is not valid.  the length must be between 0 and 4000. This is very frustrating as it is critical that I be able to pull in these tables to our staging area in order to accomplish what I need to do.  I was able to import them by going to through Access first but that is a big extra step that I would very much like to avoid.  Thanks for any additional help or guidance. 

  Top 
  Tom 
  6c3c1_sdk-qodbc.gif
 Group: Administrator 
 Posts: 5510 
 Joined: 2006-02-17 
 Profile
 Posted : 2008-09-12 00:09:53

Sorry, but this is really a SSIS/MS SQL Server issue. Try limiting the memo length to 250 characters in the QODBC Advanced Settings and doing:

SELECT Memo as "memostring" from PurchaseOrderLine where Memo is not null

 

  Top 
 New Topic 
 
 Post Reply 
[1]  

Jump to