>Thanks for the response but I may have not made my self totally clear. If you have an application installed on the server and the client is running the application Via a Shorcut Pathing to the App on the server. Then it was my impression since the application is being ran off of the server. pathing should not really matter for the OCX because the OCX is registered on the server. And as long as the application runs on the server OK then that tells me that the application knows where to find the OCX. when the application was installed on the NT machine we never had to distribute any runtime files or controls to the client because all that was being used off of the Server.
>Does this help any? if not thanks for the input anyway.

That's not true - the server's registry is not accessible to client workstations, and cannot be used to resolve registry references to COM objects except for DCOM/MTS/COM+ environments. Being registered on the server lets apps running on the server itself to resolve registry references, not clients sharing resources owned by the server.