Hi Rick -

Thanks for your input. I have a few questions about your comments....

>If you use ASP build it into a Multi-Use DLL when you build the project.
>If you're running the component on another machine (not the one you built
>on) then you'll have to register the component there using the regsvr32
>utility.

1. What do you mean by a 'Multi-Use DLL'? Is this something special or just a VFP DLL?
2. In deciding whether to build a DLL or an EXE, what would you say should be the prime consideration? Stablity? Speed? Other factors?
3. When you are talking about 'running the component'. Does this happen on the server or on the user's machine?
4. If I set up an ASP that calls my DLL, how do I setup and distribute this? Is it something that each user has to install or just something I set up on the server?


>If you do deal with data keep in mind that your server runs out of
>hte SYSTEM path with the
>resulting issues of getting at your data from there (including figuring out
>the real start directory).

1. How do I find out what the SYSTEM path is set to?
2. If the SYSTEM path is a directory on the server, how do I 'get at my data' if the data is sitting on the client machine?


>http://www.west-wind.com/articles.htm and look at the ASP Object article
>there - there are a few tips on how to efficiently use VFP components with
>ASP.

Thanks! I read your article, and at this point some of it is a little over my head, but I think it will really help me once I get into it a bit more.

Thanks again for all your help!! :)
~ellen