Do not input private or sensitive data. View Qlik Privacy & Cookie Policy.
Skip to main content

Announcements
Qlik Open Lakehouse is Now Generally Available! Discover the key highlights and partner resources here.
cancel
Showing results for 
Search instead for 
Did you mean: 
Not applicable

Newbie Issue : ScriptError General ODBC Error

Hi ,

I recently downloaded Qlikview in order to evaluate the product for my compagny

i'm currently trying to play with it.

I had built up a ODBC data source on my PC in order to acces to an MS Sql Server 2008 database

I wrote a script on QV in order to download 2 tables in by database

but i have a big issue, it does not work [:(]

ater analysis i discovered that QV is not able ti handle "integer type" colunms

in my database

Here is my script :

ODBC CONNECT TO cngrweb2 (UserId is xxxx, Password is "zzzzz");


SQL SELECT idSubnets as id,
"No_Site" as NoSite,
"vc_ipReseau" as Ip,
"i_NetworkPrefixLength" as Prefix,
"vc_modeAcces" as Mode
FROM ramage.dbo.subnets;



trace ScriptError:$(ScriptError);



LOAD "no_qos",
"libel_qos";
SQL SELECT *
FROM ramage.dbo.qos;

on table ramage.dbo.subnets

idSubnets, No_Site and i_NetworkPrefixLength are integer values

without theses columns the script works fine

any idea ?

1 Solution

Accepted Solutions
Anonymous
Not applicable
Author

The statement "QV is not able ti handle integer type colunms" is factually incorrect. Big Smile QlikView would be completely useless if this was true.
I suspect that it is ODBC problem. Didn't use ODBC for awhile, used SQL Server 2008 (and older) only with OLEDB. Can't you use OLEDB?

View solution in original post

2 Replies
Anonymous
Not applicable
Author

The statement "QV is not able ti handle integer type colunms" is factually incorrect. Big Smile QlikView would be completely useless if this was true.
I suspect that it is ODBC problem. Didn't use ODBC for awhile, used SQL Server 2008 (and older) only with OLEDB. Can't you use OLEDB?

Not applicable
Author

so i changed my ODBC driver and now it works fine Big Smile

for information :

SQL Server 2000.85.1132.00 (SQLSRV32.DLL) ODBC driver works fine

SQL Server Native Client 10.0 2007.100.1600.22 (SQLNCLI10.DLL) ODBC driver seems to have some issues