Hi,

I am using the OLDEDB provider 9.2.0.1.0 in VB6/ADO 2.7. Sometimes I notice that extra select statements are issued when I perform a query. For example, if I perform a SELECT * WFMSTAGEINPUTS another query (text follows) is issued on my behalf and without my knowledge.

Why does the OLEDB provider issue extra queries and how do I stop it from doing so?

The LockType parameter (of the Open method) is adLockBatchOptimistic
in ADO.

we use always OLE DB connection attributes - PLSQLRSet.

The extra queries like that:

select *
from
(select null TABLE_CATALOG, ac.owner TABLE_SCHEMA, ac.table_name TABLE_NAME,
acc.column_name COLUMN_NAME, null COLUMN_GUID, null COLUMN_PROPID,
acc.position ORDINAL from all_constraints ac, all_cons_columns acc where
ac.owner = acc.owner and ac.table_name = acc.table_name and
ac.constraint_type = 'P' and ac.constraint_name = acc.constraint_name)
DBSCHEMA_PRIMARY_KEYS WHERE TABLE_SCHEMA = 'ARCHIVAL' AND TABLE_NAME =
'WFMSTAGEINPUTS' order by 3, 4

select *
from
(select null TABLE_CATALOG, idx.table_owner TABLE_SCHEMA, idx.table_name
TABLE_NAME, null INDEX_CATALOG, idx.owner INDEX_SCHEMA, idx.index_name
INDEX_NAME, null PRIMARY_KEY, decode(idx.uniqueness, 'UNIQUE', -1, 0)
UNIQUE_,null CLUSTERED,null TYPE, null FILL_FACTOR, idx.initial_extent
INITIAL_SIZE, null NULLS, null SORT_BOOKMARKS, -1 AUTO_UPDATE, 2
NULL_COLLATION, col.column_position ORDINAL_POSITION, col.column_name
COLUMN_NAME, null COLUMN_GUID, null COLUMN_PROPID, 1 COLLATION, null
CARDINALITY, null PAGES, null FILTER_CONDITION, null INTEGRATED from
all_indexes idx, all_ind_columns col where idx.owner = col.index_owner and
idx.index_name = col.index_name and idx.table_owner = col.table_owner and
idx.table_name = col.table_name ) DBSCHEMA_INDEXES WHERE TABLE_SCHEMA =
'ARCHIVAL' AND TABLE_NAME = 'WFMSTAGEINPUTS' order by 8, 10, 5, 6, 17

Rgs
R.Ganesh