>Does anyone know why VFP allows you to include the Database & Tables in a BUILD EXE when they will only become RO?
>

So that you can build in read-only images of DBCs/DBFs, which can then be copied out for manipulation; in some cases, it may be desirable to include read-only data to provide an initial set of base values to use when establishing a table; eg you have a base set of default values that are added every time you create an instance of a table, so you build in a table containing those base values to use when setting up the live table. I use this approach to save a set of initial defaults for setting up a base FOXUSER resource file in my application; I know that I'm going to need to create a new instance of the resource file for the application, and if I have standard settings thatare either always included, or provide a known base starting point for common settings, it's a convenient way of getting them in place without Yet Another File to include in the distribution file set, and that has to be located at runtime - it's always findable by using a relative path, no matter where I've moved around on disk.

>Thanks
>Kev