>to save including them in the application's program folder when installing on a user's PC
No, that's decided by the exclude or incluide state of any file, not only in the OTHERs tab.
Take a look at the context menu of a file. Files excluded from compilation will not be part of the EXE built and will also have a small icon beside their name, a circle with a diagonal, like a traffic sign disallowing something. A default for that inclusion/exclusion exists for any file type. I'm not so sure all files put into the others will be included, as Mike say, but even if that's the case you can always override the default per file and there is no reason to put files here, just for getting an inclusion state.
And what is included in a setup and where which files go on a destination PC is not decided with the project manager at all, besides files being included in the EXE or DLL you build most likely will of course be installed, because you will install the EXE or DLL itself. But those files are then not needed separately anymore. More general what files are installed on a customer PC and where is decided by designing a setup and putting together whatever files with whatever absolute or generic destination folder. That's not part of VFP projects. You only have indirect influence and dependencies. If you exclude a report from compilation, you typically don't do this, because you don't need the report, but you want to be able to modify the report at runtime, so you'll put this frx and frt into a setup later. Also the setup may contain a chm help file you do with another product, or docs done with Word, or Excel Sheet templates or mdf/ldf MS SQL Server database files, and all those files don't need to be in your pjx at all. You compose the installation files in Installshield or Inno Setup or whatever setup product you use. This is separate step of your deployment and not part of the VFP project.
VFP projects are all about maintaining all files you need during development of your EXE or DLL for the one or other reason, mostly of course all the source code files compiled into the product. You can have files excluded from compilation into the EXE and also not included in a setup later, eg DOCs or txt files describing your job, or how-tos etc, which are needed for your work, but not by customers.
The only reason I see for the other tab is, it has the least important files types (menus - you mostly will have two or three per project, text files - which include .h header files, and then other files, really all other files including images, but any file extension is allowed here). So it saves two more tabs to also put in menus and text files here, but it has no special meaning.
Bye, Olaf.
