>>I am trying to avoid hard coding paths in several components I have built. Ideally, I would like to set a property (MyObject.CappStartpath) in the MyObject.init that would reflect the the path of the IIS application that has instantiated it. Something like "d:\Inetpub\wwwroot\webfax\", webfax being the application. The data is in a "data" subdirectory from webfax.
>>
>>I have figured out a two step work around when it is called from ASP but when instantiating from inside another component I'm stuck. The two step would look something like this:
>>
>>Set oTools = Server.CreateObject("WebClasses.HTMLTools")
>>oTools.cAppStartpath = Request.ServerVariables("APPL_PHYSICAL_PATH")
>>
>>
>>If I could pass Request.Server... Value to the INIT of the Object as it is Instantiated I could live with it. I would like for the MyOject.init to set it itself some how if possible. Any thoughts would be much appreciated.
>>
>>Thanks
>>
>>
>>Scott
>
>How about setting the datapath in an application registry entry? Using the Registry class in the FFC, or any one of several registry classes found here in the files section, it would take only two lines of code.

How does the component know which application it is currently working for and registerd to in that case? Just to add some more detail: I have an object that gets used by several applications. One second it could be instantiated doing work for WEBFAX and ConForm the next, both having different data paths. I am trying find a way that the COM object can set its own property based on something in the enviroment with out hard coding or passing paramters unless I have to. I hopeing for maybe some IIS object or something that would know what application it is corrently working with. I may be totally out to lunch as well...If I am what would you suggest. I started with Rick Strahl's WebTools::Init which sorta did the same thing except Application.Servername pointed to the directory to which my DLL had been built in not to the application I am Using.

Thanks again,


Scott K