"Jamie Collins" wrote:

My point was, the OLE DB provider for Jet 4.0 makes further
distinctions e.g. between Query objects that are exposed as VIEWs and
Query objects that are exposed as PROCEDUREs.

I agreed with that.

The last article I read (ADO) OpenSchema actually has 31
QueryType valus

I see that as something different, something outside of the schema
e.g. a custom Function in a VBA module (MS Access), a User-Defined
Function or Extended Stored Procedure (SQL Server). Semantics, I know,
but that's what we are discussing, isn't it <g?

My thoughts are if it is exposed by openSchema it is part of the Schema.

try to enter:
.CommandType = adCmdStoredProc
to call an excess Query
or conversely
.CommandType = adCmdUnknown
to call a Server Store Procedure

ADO will promptly inform you of your error.

I stand corrected; I reversed the two commands on
both the Command Object and the Connection Object
with no errors. I guess I should take the book "Mastering
DB Programming with VB6" back. Possible ADO may have
started to treat the two the same. I know I have read that
in more than one publication.
But either the author's are incorrect or it is not the preferred
usage or ADO has updated, but it does work.


I know there is something missing in a persons life
that would think this stuff is note worthy or interesting

OK, treading carefully here... but me being one (as you know) who
*does* find such detail noteworthy, something you said in your post
has raised my interest and you may be able to help me out with the
answer. However, I detect *you* may not be interested.

Obviously I think it is interesting but you have to realise there are
people that would put it on the same interest level as pain drying
but then they would not be reading this anyway.

something you said in your post
has raised my interest and you may be able to help me out with the
answer. However, I detect *you* may not be interested.

Of course if I can, as I'm confident you would assist me.

Good Luck
TK