Hi!

What the error message? Can you provide more details what type of crash you have? Do you know exact line of code that crashes? Your question cause too many ideas, following some of the general answers, that might help, but might not help:
1. Register run-time DLLs on the new machines.
2. Check if your COM objects registered on new machine.
3. Check exactly what crashes: maybe problem is not in the COM objects, but in something else.
4. Are your COM objects ran remotely? If yes, where are COM objects, on W2K or other machine? Sometimes DCOM works bad between dofferent Windows installations.
5. Same as above, but try to register remote COM objects in the MTS and see if it help.

>I have an application that creates two out of process VFP COM components. This has been working fine for several months but the client just bought some new machines with win 2000 and the app is crashing when trying to comunicate with the COM object. Is there a problem with VFP COM on WIN 2000 or do I need to do some thing different in the installation. I am using the FoxPro setup wizard. I have downloadded the latest setup wizard from MSFT.
>
>Thanks.