Databases Reference
In-Depth Information
After clicking on
Finish
, the configuration window will appear. Depending on the
driver you select, the configuration and parameters required for the connection
will vary. However, the configurations for almost all drivers on this, and all of the
following dialog windows, are very simple with self-explanatory fields.
After configuration, an ODBC connection can be used from QlikView in the same
manner as the OLE DB connection, just by selecting ODBC instead of OLE DB when
creating the connection string, which is described in the following section.
Let us now continue with our example using the OLE DB driver. If you followed the
process just described, click on
Cancel
to follow the OLE DB procedure instead.
Creating the OLE DB connection string
The connection string is basically a set of instructions and specifications with which
QlikView will establish the communication with the database. It contains the
database name or network location, the driver name, as well as the credentials with
which we will access the database (username and password), if needed.
The connection string is created from QlikView, so the next thing we will do is open
the QlikView document
Airline Operations.qvw
that we created earlier in
Chapter
2
,
Seeing is Believing
. We will add new tables to the data model, this time extracting
them from MS Access, to continue exploring how QlikView's built-in extraction
capabilities work.
Once the QlikView document is opened, go over to the
Edit Script
window (
Ctrl
+
E
or
File
|
Edit Script…
). We've already worked briefly with this window, and this
time, we will make use of the
Database
section in the
Data
tab.
Activate the
Airports
tab and position the cursor on the last line, below the existing
Load
statement. From the
Database
section, select
OLE DB
from the drop-down
menu, and click on the
Connect…
button, shown in the following screenshot:
