Restrictive connections and connection time
Depending on the advanced parameters defined for a restrictive connection, a
user may be required to enter database login to access data more than once in
a session for different data access actions. Some examples are listed below:
.. Defining a restrictive connection
You can define a restrictive connection as follows:
1. Open the Login Parameters dialog box. You can do this as follows:
Select Tools > Connections. Select a connection and click Edit.
Or
Select File > Parameters. Select a connection from the Connection drop down
list, and click Edit.
The login page for the selected connection appears.
2. Type a name for the connection. (You can enter up to 35 characters.)
3. Do the following:
- Type @Variable(’BOUSERPROMPT’) in the User Name box.
- Type the password for the database in the Password box.
- Type the name of your database, or connection, in the Datasource dropdown
list box.
4. Click Next.
5. Click the Test Connection button to verify the connection.
6. Click Next to access the Advanced and Custom parameters pages. Fill in
parameters as required.
7. Click Finish on the Custom page.
Advanced parameter Effect on connection activity when selected...
Keep the connection
active during the whole
session
User is prompted to enter database login parameters
on the first refresh of a report, but not for subsequent
refreshes. However, if the user starts the SQL parser
to validate a SQL statement, then they could be
prompted to enter database login to run the SQL
check.
Disconnect after each
transaction
User is prompted for database login on each
document refresh, or each time a query is run.
Partager