I have used command object a lot, mostly in the "right" way that has been mentioned. I think that a clearer example of the wrong way could have been explained. If you how wrong something can be, then it will be easier to understand why not to follow in that direction.

I have tried to use the Command object in the past, although I have been able to use input paramaters I have been unable to use input/output or just output, can you explain a little more in depth about those? Also is there any benifit to using the ADO "Hints" over the constants?

You might want to look at a later article I did that covers a VB add in that will generate the command object code for you, a real time saver. I use output params regularly with no problem, just a matter of getting everything set up right. What hints are you referring to?

I do a lot of Web development and one of the problems I find is that the constants (adCmdStoredProcedure) used to indicate command types are rarely defined outside of an MS app. For example, I use DreamWeaver quite a bit.

I have the ADO2.6 command reference book, and yes, in appendix B it has the definitions of these constants, but wouldn't it be great if someone wrote a book that listed the constants and their values before the example code?

Incidentally, I have a problem where I am trying to access two separate databases within a Site Server implementation.

If I have a page that accesses my user database using my connection string then everything works OK. Ditto the Site Server functionality.

If I try and use both together on the same page everything goes beserk!

I have tried defining two separate connections but I keep getting Accessed Denied error messages.

Both SiteServer and my user databases are using Windows Integrated security. Both have the required user set up and yet I still get Access Denied!

If I use SA then I am allowed in but there is no way I want to release a piece of code that uses the SA login and password!