I've done this on a Netware server and though I can't be 100% sure I'm positive it would be the same for NT.

The ActiveX controls need to be registered on each users machine. So do the DLL's for the VFP runtime. Create a setup exactly the same way you would for installing the exe on the users machine but exclude the exe from the setup. HTH

>Can a VFP app (exe) that contains ActiveX controls reside on a network server? Do the ActiveX controls need to be registered on each NT workstation or can the ActiveX controls be registered one time on the NT server?
>Hi all,
>
>I have developed VFP apps w/ActiveX controls where the database was located on the NT server and the program files including ActiveX controls were distributed on each workstation via a setup program on the server. I had a version check by comparing the version field in the system table on the server with the version field in the system table on the workstation. If the versions did not match, the user was informed to run the update program on the server which would scan their local drive and locate the program directory and update the program files to the latest version. I found this to work very well.
>
>However, on my new assignment, the upper management wants the program files and the database to reside on the NT server and not on the individual workstations. If the ActiveX controls need to be registered on each workstation, then the method I described would be the best way to distribute the program. If the ActiveX controls can be registered one time on the NT server, then the way they want the program setup should work??
>
>Any comments, personal experience, help along these lines would be greatly appreciated.
>
>TIA,
>
>James Moore
>Ministry Tracking Software