I am building websites using Databases and COM for 3tier apps.

Currently I have to tell my COM object where the database is located either
1)  Hardcoded in the DLL
2)  Via my ASP call

How do I retrieve the dir where my DLL is located?
In the VB6 runtime environment "CurDir" does it for the runtime-situation
Once I go "DLL" CurDir is retrieving the current active dir, that could be
anything.

Is a solution present by Microsoft?

== This is Where I want to go to:
I want to create/call something inside the DLL like "thisDLLpath" (read: any
VB instruction doing just that)

When the DLL is located in "c:\myDLLs\testDLL", the call "thisDLLpath"
within the DLL should return just that.
When I move the DLL to "D:\myDLLs\finalLocation" (on another server), the
call "thisDLLpath" within the DLL should return just that

== Why?
When building websites using 3tier, currently I need to set the full path
(or the ODBC name) to the database in either:
1)  my ASP script
2)  the ODBC manager

Just using the DLL with thisDLLpath enables me to cut away extra settings
and place the DB anywhere. It is less rigid (copy & paste DLL and DB into a
Dir, register the DLL and presto!) Working on two or three different servers
it is the most flexible way to go.