I think you found your solution. <g> Keep in mind that with WC you have lots of options of how you want to persist connections, although ASP style connection caching is not one of them.

The best way IMHO, is to use wwSQL, hang a reference off the server object (call it oSQL) load it in SetServerProperties with a connection string from the INI file, then forget about it. In your process code you simply reference Server.oSQL.Execute() or whatever you need.

You can take this a step further if you use business object by passing that SQL object (or the SQL handle property if you choose) to the bus object so you can use that single connection trhoughout any SQL access.

It's very flexible because you can decide how you want to deal with the connections...


+++ Rick ---



>Hi Michael:
>
>When the three COM instances instantiate I would like to make a connection to SS and have connection available to Process method where code executes. Where is a good place to do so? I have tried INIT method of WebProjectconfig (comments say it hold props for life of server) class, but prop values seems to change when I reach Process class where my code is supposed to execute.
>
>Thanx,
>Charlie