I am using ASA 7 and have been advised to use COMMIT when using SELECT
statements in order to prevent locks being left on tables. I have
never expereienced this behaviour with any DBMS that I have used and
not with Sybase either - Uncomitted Trans in DBWatch+ is always
reported as 0.

I would be grateful for advice either way.

Yahoo Sirius wrote:

That advise sounds like hooey from an oracle SQL-plus-centric DBMS novice.
(The SQL-PLUS user program for Oracle operates in 'chained, autocommit(false)
mode.)
Forget it. Sybase connections operate by default in unchained, autoCommit(true)
mode, so unless you've explicitly changed that by changing the session to chained
mode or defined a transaction with 'begin transaction', the DBMS releases
all locks by the time the query is finished.

Joe Weinstein at BEA