topic It's possible block function ODBC Select or Connect in Qlikview Desktop in QlikView

It's possible block function ODBC Select or Connect in Qlikview Desktop

Sat, 21 May 2011 15:52:17 GMT

Hey Guys. It's possible block or disable ODBC Select or Connect function in Qlikview Desktop. Thanks a lot.

It's possible block function ODBC Select or Connect in Qlikview Desktop

kaushiknsolanki — Sat, 21 May 2011 17:15:52 GMT

No its not possible until i know. Cause that is designed in wizard only.

Can you describe why you want to disable it

Regards,

Kaushik Solanki

It's possible block function ODBC Select or Connect in Qlikview Desktop

Oleg_Troyansky — Sat, 21 May 2011 23:10:37 GMT

There is no way (that I'm aware of) to disable database functions in the script. If you need to protect your databases from unauthorized use, you should define it in the database security rather then in QlikView...

It's possible block function ODBC Select or Connect in Qlikview Desktop

Mon, 23 May 2011 04:06:16 GMT

Thanks for your answer. I Have a ODBC Database create with a user what can see all tables and that user is stored in the same ODBC. the idea is block this ODBC no delete just block in Qlikview, because this ODBC is used in other programs.

It's possible???

Thanks.

It's possible block function ODBC Select or Connect in Qlikview Desktop

Sat, 28 May 2011 00:34:24 GMT

When I read your questions, I think you are asking how to restrict the connection to the database to read only.

There are two ways, basically.

First, you can use the same user you have set up now. While the user permissions are full, you may change the ODBC connection string to restrict to READ ONLY.

See:

DBPROP_INIT_MODE

http://msdn.microsoft.com/en-us/library/ms722656%28v=vs.85%29.aspx

If you use the QlikView wizard to connect via ODBC, that will give you the basic connection string, modify as you like to restrict to read only.

Second, you could create a new database user which is read-only and specific to the application, in this case QlikView. After you do that, use those new credentials to read data into QlikView.

The second way is standard practice in most organizations, because it gives the DBAs good information about which machine/process is accessing data, when and how.

Hope that helps.

Sam