In the DB Interface Module paradigm, all results are tables. Class RWDBTable encapsulates a single result set, class RWDBResult encapsulates a sequence of 0 or more tables, and class RWDBReader provides the mechanism for reading a table. Consequently, handling multiple result sets is not a problem.

In the DB Interface Module, the execute() method of each DML class returns an RWDBResult object. Applications that are concerned with results returned by an INSERT, for example, can maintain portability between databases by checking the RWDBResult returned by RWDBInserter::execute().

Any data not processed by an application is silently discarded. The DB Interface Module applications need not explicitly discard results; they need not consider the state of the database connection. Data is exchanged between the ODBC driver and the DB Interface Module via ODBC function calls. The statements associated with these calls are either explicitly closed by the Access Module or, if processing multiple results, implicitly closed through a call to SQLMoreResults(). So any data not processed by an application is silently discarded; SoucePro DB applications do not need to consider the state of the database connection.

The DB Access Module for ODBC queries the underlying database ODBC driver for the maximum number of simultaneously active SQL statements (SQLHSTMT) allowed per connection by the driver (SQL_MAX_CONCURRENT_ACTIVITIES). If a connection is used for a new operation, but already has the maximum number of simultaneous operations active, the results of the oldest operation are silently discarded.