Erik and Nick,

I thought I had posted a reply to this before I went to lunch, but it's not showing up, so I will post again.

>The serve is running on the remote box. Any files it accesses need to be pathed relative to that server, not the client. IOW, if you are using data files that reside an the server, you would use c:\Data\MyDatafile.
>

Doing this solved one of my problems. I did note however that I had to add .dbf to the end of the table name in order to use the table. The dfox example did not do this.

>>Also, is there some way to get the server to show up under applications in dcomcnfg with the ability to set the security context, etc... specifically for that server?
>
>As long as the server is registered and is Out-of-proc (it has to be for DCOM), then I have never seen a situation where it didn't show up. Did you also check under its CLSID?

I'm assuming that any com server that is an exe file that is registered is out of process, but if I'm wrong about this, please correct me. Mine is an exe file I registered via

c:\dfox\dfox.exe -REGSERVER

I've carefully looked through the applications listed in dcomcnfg and can't find my server listed under either it's name or clsid. This is also true after registering the server on my win2k pro box at home, so I figure there must be something else I'm doing wrong if it fails on 3 windows versions.

Any ideas on how to fix this would be greatly appreciated.

regards,

JE