ADO Connection objects are apartment threaded by default. You'll suffer from thread affinity if you place the connection OBJECT in a session/application scope variable...<BR><BR>However, it is perfectly acceptable to place the connection STRING in a session/application scope var.
You CAN change the threading model of ADO to be 'Both' <and therefore making it threadsafe to place into that level of scope> but it seems like too much trouble for what it's worth.<BR><BR>Why muck with the registry if you don't have to. They made it apartment by default for a reason, right? Apartment threads run much more efficient when used properly.