>Sorry I wasn't clearer. What I mean is that I am building a part of a tiered application.
>
>1. Web server presenting all data. .ASP pages making COM calls as necessary.
>2. DCOM server doing all business logic. Same server doing entitlement logic. Same server possibly acting as a read-only cache database.
>3. Database server (maybe/maybe not with COM objects running on it).
>I am pushing VFP as a good fit for this "in the middle" server because I can use a VFP DBC for the cache-only database (all mission critical data gets written to MSSQL and only ends up here as needed) and I can do the business data logic. VB COM for security stuff.
>
>I can't export the MTS package to desktops because the clients are all web browser based.
>
>The web servers will probably be outsourced to someone with an ironclad SLA. But the COM servers and database servers will stay on my site.
>

In that case, the MTS packages get exported to the web server. I am curious why you see that VB should be used for security.



>
>
>>Make it easy on yourself. Export the MTS package. You'll get a client install program. Run this on the clients (even if other servers). Bingo! You're done!