>Server must exist both on the client and the server (or at least the typelibrary) if you use the ProgID (someserver.someclass). If you use the CLassID for the server that requirement goes away.
>
>You also will have to deal with access permissions to the server. By default Windows 2000 doesn't allow remote access to any objects even by administrators. You need to configure this with DCOMCNFG.
>
>Take a look at:
>
>http://www.west-wind.com/articles.asp and look at that Internet Enabling article there...
>
>+++ Rick ---
>

Thanks Rick, having your article already printed for months in my to-read pile, I had the explanation under my nose…

Another question about the same project:

From Internet Enabling:
"Here you can see the problem with a file based database tool like VFP – it does all of its processing on the client side, so while the data sits on the server with a slow connection the client needs to pull all the necessary data to perform lookups and get the data itself, which may require significant amounts of the data locally causing much traffic to occur over the network connection..."

This is precisely what I want to workaround, my COM server will do data processing on the server and will return data wrapped in objects.
I suppose that being COM-compatible they can be used by VB too (faster forms in Winframe) or be transmitted over the Net. Or am I wrong?

Agustin