Very Computer

Greetings,

I am using the ADOX, (Shipped with SQL 7.0) and I am having a problem
getting the command object that represents a stored procedure. The
documentation says the following will retrieve a command object with the
stored procedure and parameters.

(Assuming an open connection)

' Open the catalog
Set cat.ActiveConnection = cnn

' Get the command object
Set cmd = cat.Procedures("CustomerById").Command

However this doesn't seem to be the case. It will not allow me to make the
assignment.
I look at the ADOX in the object browser and I see that the return value of
the procedure.command object is a Variant (where in other parts of the model
actual objects are returned.)  If I add a watch to the procedure object
while the app is running, It will only show me the Name, Date Created, Date
Modified properties correctly.

I was primarily looking for a confirmation of this behavior by someone
besides myself to see If this is an isolated problem maybe with my
configuration, or If others were experiencing the same problem.

I appreciate any response

Thanks,
Scott Johnson

Found my own answer.. And just for anyone who's interested:

Microsoft found it necessary to publish a set of documentation on the MSDN
Jan99 about
these great new extensions for DDL and Security called the ADOX. (Which
ships with MSSQL7)

When one reads through these documents they sound great, In my case it
looked like It could simplify
reading through database structure and save a lot of headaches when it comes
to stored procedures, and finding the parameters...  Gee, Silly me for
paying attention to this stuff my company paid really good money for.

Look at article: Q198534 & Q198535 On the MSDN-Online... The Read-me for
what they left out of the ADOX. (Actually they blame it on the OLE-DB
providers, but they make and distribute these in the same package...)

I will chalk this one up to another big waste of my time. Back to the Old
OpenSchema methodolgy.