In the following example, db_check creates a database checkpoint. "list_1.cdl" is the
name assigned to the database checklist captured for a test script; "dbvf1" indicates the
expected_results_file captured for this test.
In the following example, db_check creates a database checkpoint. The parameters for
the SQL statement are in an array in the fourth parameter of the db_check statement.
param_array = 3;
param_array = 7;
db_check ("list1.cdl", "dbvf1", NO_LIMIT, param_array);
The connection parameters to the ODBC database.
In the following example, WinRunner creates the "query1" database session and
establishes a connection to an ODBC database using the "DSN=Flight32" connection
session_name The logical name of the database session.
SQL The SQL statement.
record_number An out parameter returning the number of records in the result query.
The db_execute_query function executes the query based on the SQL statement and
creates a record set.
In the following example, WinRunner executes the query based on the "SELECT *
FROM Orders" SQL statement and creates the record set, which has record_number
The index of the row written as a string: "# followed by the numeric index.
(The first row is always numbered "#0".)
Either the name of the field in the column, or the index of the column within the database written as a string: "# followed by the numeric index. (The first column is always numbered "#0".)
The db_get_field_value function returns the value of a single field in the specified
row_index and column in the session_name database session.
In case of an error, an empty string will be returned.
In each of the following examples, WinRunner returns the value of a single field in the
"query1" database session.
In the following example, WinRunner returns the number of column headers in the
"query1" database session and all the strings in all column headers, concatenated and
delimited by tabs.
ChecklistFileName A file created by WinRunner and saved in the test's checklist
folder. The file contains information about the data to be captured during the test run and
its corresponding field in the database. The file is created based on the information
entered in the Runtime Record Checkpoint wizard.
An out parameter returning the number of records in the database.
The db_record_check function compares information that appears in the application
under test during a test run with the current values in the corresponding record(s) in your
In the following example, db_record_check creates a runtime database record checkpoint.
"list_1.cvr" is the name assigned to the checklist captured for the test script;
"DVR_ONE_MATCH" indicates that the checkpoint will pass if one, and only one,
matching database record is found.
The name of the data table. The name may be the table variable
name, the Microsoft Excel file or a tabbed text file name, or the full path and file name of
the table.The first row in the file contains the names of the parameters. This row is
labeled row 0.
mode The mode for opening the data table: DDT_MODE_READ (read-only) or
DDT_MODE_READWRITE (read or write). When the mode is not specified, the default
mode is DDT_MODE_READ.
The ddt_open function opens the data table file with the specified data_table_name. The
active row becomes row number 1.
The ddt_close_all_tables function closes all open tables in all open tests. Note that this
includes any tables that are open in the table editor, tables that were opened using the
ddt_open or ddt_show functions or/and using the DataDriven Tests Wizard.
In the following example, Test2 begins with the ddt_close_all_tests
function in order to close any open tables from any other open tests.
The destination data table filename.
The ddt_export function sends the contents of data_table_name1 to data_table_name2.
In the following example, WinRunner exports the information from the Excel file entitled
"Default" to the Excel file entitled "flight".
Now bringing you back...
Does that email address look wrong? Try again with a different email.