>Mike
>
>Thank's
>
>Your response is a GREAT HELP for me but could you confirm me some details.
>
>1/ vfpasp.vfpasp
> ^ ^
> | |
> | +-- is a VFP custom OlePublic object
> |
> +-- is a DLL generated from VFP -
>

Yes, vfpasp.vfpasp is a custom OlePublic object. The automation server can be generated either as an In-Process DLL or Out-of-Process EXE. The testing I've done has typically been Out-of-Process but it should work either way. If you choose to use In-Process servers then you will have to deal with the associated threading problems with VFP.

>2/ "Test" is a custom method from the "vfpasp" custom OlePublic object.

Yes

>3/ "Request" and "Response" are collection "classes" available in an ASP script and sent to the VFP automation server.

Yes

>
>4/ What is MsWc ?
> On my computer (W95), I only find MsWcRun.dll and MsWcRun.dep and on our
> server (NT), I did not find anything.
> On MS site I found "Q168269 = MSWC BrowserType Control Does Not Recognize
> IE 3.02" in a kwonledge base search.
>

This is an ASP browser type component. It calls the Browscap.dll to provide client browser information. You may not have it available on the personal web server - depends on which version. Look under the ASP component reference help for Browser capabilities for additional info. You do not have to use this component but it was in the example code since I needed information about the client's browser within VFP at the time.

>Thank's in advance
>
>Stéphan (beginner in web application)