Skip to main content
Announcements
Join us at Qlik Connect for 3 magical days of learning, networking,and inspiration! REGISTER TODAY and save!
cancel
Showing results for 
Search instead for 
Did you mean: 
Not applicable

ODBC problem

Hi guys, here is the situation:

QV 9.00 SR6

platform/OS - Win7

ODBC used - 32bit - 4D Server

Problem:

I want to select several columns of a database table. With some columns it works fine; others not

Some columns have very long lenghts (text). Because of this (i guess) I cant query the hole table. It would be enough if I select for instance only the first 50 characters of each cell of this problematic column.

Has anybody a solution of this.

Thanks and regards,

Matthias

4 Replies
pover
Luminary Alumni
Luminary Alumni

There's not much QlikView can do to control what the ODBC returns as data since the ODBC is an independent component.

Maybe this post will help you.

http://community.qlik.com/forums/t/37833.aspx

Regards



gfarrell
Partner - Contributor III
Partner - Contributor III

Hi,

Did you try limiting select to the first 50 characters in the sql select? Alot of databases have a 'left' function....like SQL Server. ex: left(column1,50) .

Others like Oracle have a substring function ex: substr(column1,1,50)

Not applicable
Author

Hello, I will try to limit the characters (tomorrow morning in my office).

In the meantime (by analysing the data) I guess the problem is not the length of the data. It is the special content. There are sometime special signs like ? => in some cells. Maybe it will be able to export the database table via excel or access and delete this special signs. Then I will try it again. If this works, I need a automatically solution.

Thanks in advance

Matthias

Not applicable
Author

Hello to all,

thanks for your help. I have found a solution. There were a ? in one field, which caused the ODBC-problems.

Case closed

Matthias