Yes, developed, deployed, run on all Windows 2000.

>Are the clients W2K too?
>
>I remember having some problems when testing client installs created in W2K (COM+) and running them on NT workstations.
>
>Check out this MSKB and see if it helps: http://support.microsoft.com/support/kb/articles/Q259/7/19.ASP
>and also http://support.microsoft.com/support/kb/articles/Q289/8/21.ASP
>HTH
>
>>UI EXE and BO DLL resides on each client computer and Database Objects DLL resides on the server as COM+ package. I created client setup from COM+ and ran the setup on each client. I could instantiate these object proxies from a client computer but for some reason, it appears my BO DLL that communicates with the remote DO DLL isn't working.
>>
>>>What's the setup? I mean, where does the front end, BO DLL reside and are they separate from the server.
>>>
>>>Maybe you are missing some runtimes on one of the machines.
>>>
>>>>Well, I still can't get it to work. I don't know why but my BO DLL isn't correctly trying to run the remote server DLL although remote server DLL is installed and working correctly.
>>>>
>>>>I could instanciate a method of the remote server via VFP command window and watch the ball spinning but I can't figure out why my BO DLL isn't trying to call "this" DLL.
>>>>
>>>>>Windows 2000 Professional on all workstations so I know it's not DCOM problem. I do, however, think I found an answer but I'll have to try it out first.
>>>>>
>>>>>It seems logical that when I compiled my business objects DLL it was referencing the Data objects (server) DLL of the project (e.g. local) instead of the remote proxy DLL installed on the server. I'll recompile my BO DLL referencing the remote DLL and see if this fixes the problem.
>>>>>
>>>>>>What OS are the clients running? You need DCOM support for clients to work with a remote object. NT & W98 both come with the support, and in W95 you have to install it.