Hi Anatoliy,

You don't want to store anything in the registry for a Web application - Registry access is synchronized, so multiple simultaneous requests will queue... bad idea <g>...

That really just leaves a file in the same directory as the DLL. Open the file in SHARED mode to read it to avoid queuing. It's not really elegant either, because it has to be read on every hit and there's overhead in reading that file just like anything else but it work. You can also use a config free table with the same scenario which might be easier. The key is to put the file in a known location which is likely the same directory as the DLL (which you can find with Applition.ServerName) or in the Web path somewhere wher you can find it with the ASP Server.MapPath() functionality.

+++ Rick ---




>A web service based on VFP MTDLL runs under IIS 5.0 on W2K. What is the best way to store config settings that can be read from VFP MTDLL code?
>
>I tried to store path to a database in Windows Registry -- IUSR account can not read the registry. Which is Ok, otherwise it would create a security issue.
>
>What could be other options?