>>>>1) When I finally go to distribute my program, on which I've been slaving for so long, how do I know which files I need? Is there a list of file extensions anyone has which are required to include with the distribution disks?
>>>>
>>>>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)?
>>>>
>>>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.
>>>
>>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
>
>All the files needed for the application should be included in your project, except for the database (.DBC) and the tables (.DBF, .CDX, .FPT). I also exclude the bitmaps (.BMP), the cursors (.CUR), the icons (.ICO) and the include file (.H) so that I only need to send a new file to update a bitmap for example.
>
>So, with your .EXE, you need: .DBC, .DBF, .CDX, .FPT, .BMP, .CUR, .ICO, .H and .HLP
>
>You don't need to send the other files if they are included in your project.
>
>HTH
Well, with the help of Sylvain Larin, Chris Reed, Barbar Paltiel, Bret Empie, Gary Goodwin, and Tony Miller, and much testing, I've learned the following:
When building a project, the only file types needed to be one the initial set of disks are:
Initial installation file requirements:
-----------------------------------------------
CDX
DBC
DBF
DCT
EXE
FPT
FPW
OCX
For all updates OTHER THAN dbf structural or CDX index changes:
---------------------------------------------------------------------------------------------
EXE -- that's it! I've personally tested updating a report, form, and menu, all of which showed the changes by only updating the EXE file!
All of you were quite helpful in answering my question -- I'll look into Install Shield; I assume that's the best thing going for VFP customized installations. If anyone has that list of files to be used for un-installation, I'd be interested to see it.
Thanks again all of you!
Sincerely,
Mark W. Mitchell
mark@remarkable-systems.com
