Connect

The CONNECT statement is used to define Qlik Sense access to a general database through the OLE DB/ODBC interface. For ODBC, the data source first needs to be specified using the ODBC administrator.

Note: This statement supports only folder data connections in standard mode. See File system access restriction

Syntax:  

ODBC CONNECT TO connect-string

OLEDB CONNECT TO connect-string

CUSTOM CONNECT TO connect-string

LIB CONNECT TO connection

Arguments:  

Argument Description
connect-string connect-string ::= datasourcename { ; conn-spec-item }

The connection string is the data source name and an optional list of one or more connection specification items. If the data source name contains blanks, or if any connection specification items are listed, the connection string must be enclosed by quotation marks.

datasourcename must be a defined ODBC data source or a string that defines an OLE DB provider.

conn-spec-item ::=DBQ=database_specifier |DriverID=driver_specifier |UID=userid |PWD=password

The possible connection specification items may differ between different databases. For some databases, also other items than the above are possible. For OLE DB, some of the connection specific items are mandatory and not optional.

connection

The name of a data connection stored in the data load editor.

If the ODBC is placed before CONNECT, the ODBC interface will be used; else, OLE DB will be used.

Using LIB CONNECT TO connects to a database using a stored data connection that was created in the data load editor.

Example 1:  

ODBC CONNECT TO 'Sales

DBQ=C:\Program Files\Access\Samples\Sales.mdb';

The data source defined through this statement is used by subsequent Select (SQL) statements, until a new CONNECT statement is made.

Example 2:  

LIB CONNECT TO 'DataConnection';

Connect32

This statement is used the same way as the CONNECT statement, but forces a 64-bit system to use a 32-bit ODBC/OLE DB provider. Not applicable for custom connect.

Connect64

This statement is used the same way as the as the CONNECT statement, but forces use of a 64-bit provider. Not applicable for custom connect.

See also:

 

Did this information help you?

Thanks for letting us know. Is there anything you'd like to tell us about this topic?

Can you tell us why it did not help you and how we can improve it?