We had a system that we ran the updates through that removed all the code.

The app where we had everything excluded was auto updating - was very cool. We (developers) ran an application (VFP) that placed the files in a directory where the clients application would pick them up automatically. Once the client application had the files, it updated itself, and then updated all the users in the system. The client application was set to automatically dial in to our office daily to send files for billing (this was an insurance clearinghouse for hospital billing). This application was installed at over 1000 sites (FPW and VFP). The client could run the job manually as well.

One big reason for the breaking down of the files was because the users would dial in to send files, receive files, and get updates. We did not want them to spend hours getting an exe - when we could much more easily just give them a fr? or sc? or vc?, etc.

The system could be updated every night because of the hundreds/thousands of different rule components the client could have depending on what types of insurance coverages they accepted. Those were compiled into programs...

-w-



>>It works very well. There is really no need to create apps... just use the same directory structure and drop the files in the appropriate directories.
>>
>>It makes updates very simple. I have had an app where everything was broken out (Excluded), and have a current one where only the reports are excluded. It makes it very simple to update a report without changing the exe.
>
>Thanks for your comments just a quick question: What about the fact that the advanced customers could open the form's source code in a copy of VFP and change the forms to suit their needs possibly even recreating the application on their own?
>
>BR
>Tim