>I have a complete internet application which runs based on the old foxpro search page sample using vfpcgi.exe. I have a client who wants to change the whole thing to use ASP with the web server software written in VFP as COM or DCOM objects.
>
>I have a routine that loads all of the setup information from a free table when the application launches. However, since each request will now be a separate process and will need to load setup variables, what is the best way to store/load configuration information? I am primarily concerned with the performance aspect, but of course something that is really easy to code is good as well. Should I leave config info in the table? Should I put it in the registry? In an INI?
>
>All opinions are appreciated.
>
>Thanks,
>
>Paul R. Moon

Are these simple type values? And are they the same for any request / session?

If yes to both questions, you might want to consider putting these settings in application-level variables of your site. In this way they will be readily available (and accessed fast) for any web site user.

Just add them to your application's OnStart event (on global.asa file).

Sub Application_OnStart
   Application("mySetting1") = "Value"
End Sub

HTH