|
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
|
|
| Memo 4095 length too long for ODBC query to SQL Server 2005 |
| Author |
Message |
|
|
| Posted : 2007-06-30 12:16:22 |
| I am using QB Pro2005, QODBC 7.00.00.214, SQL Server 2005 all running on Win2003 server. I have successfully used ODBC to query tables but Memo field in Invoices gives message: * Error 0xc0204016: DTS.Pipeline: The "output column "Memo" (21)" has a length that is not valid. The length must be between 0 and 4000 -- I know that Nvarchar has length limit of 4000 characters but Varchar should support 8000 characters. I have tried mapping Memo to Varchar and to Text but always get the same error. I am not the only one with this problem--see http://www.experts-exchange.com/Microsoft/Development/MS-SQL-Server/Q_21904486.html |
|
|
|
| Tom |
 |
| Group | : Administrator |
| Posts | : 5510 |
| Joined | : 2006-02-17 |
|
| Profile |
|
| Posted : 2007-06-30 20:38:02 |
Text Field Handling has been added to QODBC v7.00.00.204 and later. Try checking the Convert Fields > 255 to LONG VARCHAR and Limit length to 3992 characters. These fields help some development environments get data from long fields that would not be able to otherwise.
Connection string options include: ConvertToLongVARCHAR=Yes|No and MaxLONGVARCHAR=4096.
|
|
|
|
|
|
| Posted : 2007-07-03 05:57:11 |
I changed the settings as you suggested but same result. SQL Server 2005 still generates this error:
Operation stopped...
- Initializing Data Flow Task (Success)
- Initializing Connections (Success)
- Setting SQL Command (Success)
- Setting Source Connection (Error)
Messages
* Error 0xc0204016: DTS.Pipeline: The "output column "Memo" (21)" has a length that is not valid. The length must be between 0 and 4000.
(SQL Server Import and Export Wizard)
* Error 0xc0047062: Source - Query [1]: System.Runtime.InteropServices.COMException (0xC0204016): Exception from HRESULT: 0xC0204016
at Microsoft.SqlServer.Dts.Pipeline.Wrapper.IDTSOutputColumn90.SetDataTypeProperties(DataType eDataType, Int32 lLength, Int32 lPrecision, Int32 lScale, Int32 lCodePage)
at Microsoft.SqlServer.Dts.Pipeline.DataReaderSourceAdapter.ReinitializeMetaData()
at Microsoft.SqlServer.Dts.Pipeline.ManagedComponentHost.HostReinitializeMetaData(IDTSManagedComponentWrapper90 wrapper) (SQL Server Import and Export Wizard)
* Exception from HRESULT: 0xC0204016 (Microsoft.SqlServer.DTSPipelineWrap)
- Setting Destination Connection (Stopped)
- Validating (Stopped)
- Saving (Stopped)
Any other suggestions? |
|
|
|
| Tom |
| |
| Group | : Administrator |
| Posts | : 5510 |
| Joined | : 2006-02-17 |
|
| Profile |
|
| Posted : 2007-07-03 08:15:30 |
| Unless you have changed your SQL Server connection string, you will need to unlink QODBC and relink. |
|
|
|
|