>>
>>Here's what I did to solve the problem of network installations in general. I first created a setup program (I called it Install.EXE) that did the following: It deleted itself from the group that it was in, and added the application into that group. Naturally, it first looked at F:, but if it could not find the path, searched the other networked drives until it found it. I made sure that the users had access to the directory prior to having them install. I next created a project containing all the necessary components ESL, OCXs etc. and built the EXE.
>>
>>The key here is to indicate in the Setup Wizard that the install program is to be run when the base installation is complete. Finally, I placed the installation disks on the network as a children of the main application directory. This way, if they had access to the child directories, they had to have access to the parent. Also, it allowed installation without disk swapping or distribution.
>>
>>One last note, I had the install program installed on the user's C: drive, and used that directory for the CONFIG.FPW and temp files.
>>
>>HTH,
>>
>>George
>
>It appears that the Project needs to contain the ESL and OCX - from what George said so I'll try that - thanx
>
>Ed B

Ed,

See the help file or chapter 26 in the developers' guide, for a list of what needs to be where. Niether the library nor the ActiveX controls need to be included with the project.

George