Thanks Craig!

Best

-Gary


>>Craig:
>>
>>Very many thanks for replying.
>>
>>>Install MTS from the NT4 Option Pack. Then, host the component in MTS. You can then export a client SETUP that is simply an EXE that will need to be run on the client stations on the LAN. They will then have access to the component.
>>
>>OK. Is there any special handling/calling of the COM server required (from within VFP) when it is run in MTS?
>
>You call it as you normally would. There is an article on VFP and MTS at http://msdn.microsoft.com/library/default.asp?URL=/library/techart/MTSVFP.htm
>
>>
>>The current server is a WinNT Small Business Server but this is going to be upgraded in a couple of months to SBS 2000 which is based on Win2000 server. I presume this changes the equation. How would this affect things? I have it in my mind that MTS in Win2000 is part of COM+ ?
>
>Yes, it is. I have a COM+ whitepaper on my web site and an upcoming series of articles in FoxTalk.
>
>>
>>>You'll call the VFP component from the ASP page for from WebConnect.
>>
>>Remote access to the component will be from a VFP desktop application. This application will allow remote, validated data entry and when complete, it will (hopefully) connect to the COM server via Internet dial-up and pass the appropriate parameters. Presume this scenario is OK.
>>
>>> or a parameter object.
>>
>>Wow, this sounds cool. Could you enlarge on this?
>
>There is a whitepaper at www.comcodebook.com.
>
>>
>>Craig. This is just the sort of information I need. I really appreciate your advice.
>>
>>Later.