When I added the Test Object Script I meant to also add a script that allows you to test a database connection.

Test Database Connection Script

To use: Save the target to disk; change the file extension to .vbs; launch the file and enter the connection string of the object you want to test.

Remember that if you are using windows authentication then you will have to test this script running as the trusted user; which possibly isn't the same user as your login, especially to a server.

I posted this small VBS file a few weeks ago I also suggested that having the path to the com object would also be great.

My prayers have been answered

When I place new COM into a different environment I find that the new environment is running with a different set of DLLs or missing dome DLLs from my development machine. This VBscript has been more than helpful.

It's very simple in all it does is try to create an object from a ProgID. Now what would be nice is if successful to get the path to the object...

To use: Save the target to disk; change the file extension to .vbs; launch the file and enter the ProgID of the object you want to test e.g. ADODB.Connection.