>>>2) Let's say now you've helped me on #1, but now it's time for me to update a piece or two of my program -- how do I know which files to update on my customer's machine? If I update or create a form -- do I just install the SCX and SCT files for that form, or perhaps the EXE of the project file? What about modifying a report? Which file(s)?
>>>
>>>Please help!
>>>
>>>Thank you!
>>>
>>>Mark W. Mitchell
>>
>>Hi Mark,
>>
>>The rest of the thread has talked about (1). For the second half, you should only need to update data structures (if changed), reports and the EXE. Classes, PRGs and forms are included in the EXE.
>>
>>HTH
>>Barbara
>
>
>Barbara,
>
>Thanks for the assistance! This last portion was really helpful. Tony Miller made a good suggestion, but perhaps I didn't make myself clear in #1. I am using the VFP setup program. For my purposes, it works fine (for now), but when I'm developing a project, this directory becomes filled with 'extra' files (like .BAK, etc.). These files need not be included in the distribution disks so I've made a directory below the working for distribution files only. I then use a batch file to copy all files with certain extensions to this distribution directory; that is why I needed the list. I do not wish to pack up all the project files and re-install on the client's machine when I make a simple change (such as on a form, etc.) I now know, thanks to your advice, that changing prg's, forms, and classes, only requires re-distribution of the EXE file. I'm assuming the following for some of the other changes:
>
>reports: FRT & FRX
>menus: MNT & MNX (or should it be MPR & MPX ?)
>
>Do I need:
>---------------
>QPR & QPX ?
>H ?
>HLP ?
>PJT & PJX
>
>tia!
>
>Mark

Sylvain's answer covered almost everything. Report files (FRX/FRT) are 'optional'. If you don't think they'll be changed, they can be included in the EXE. Most of us leave them out and distribute them separately because it's easier to send a client 2 small FR* files than a whole new EXE.

Barbara