Hi Sally

I have just ventured into VFP from DOS and using CodeBook 6.2 for developing the initial apps. I have a similar idea and had a similar question put up on UT. The suggestion I got was to use subclass of all the common module into your 30 apps so you can just change the base class of yours and the changes are propagated. As for icons you can specify them in the subclasses and they won't be forgotten.

Hope this helps and if you get a better response or idea please let me know. I was thinking about this as I have a regular demand for specific modules like Accounting, Inventory, Excise Docs, Order Processing, Export Docs. But generally the clients want a combination of these modules and not all. Also there are customizations to these so the subclass idea looked okay to me.

I am still a beginer and have not yet got around to the subclassing but soon.

>I have approx 30 software products built on the same basic engine using VFP6. Each of these has a project however the projects are very similar. The only differences between them are the icons and the menus. I have removed the data from the projects. I want to be able to base all the 30 programs on one project and build all 30 executables by running a vfp program. This program will need to change the icon and the menu location for each project and name the executable a different name. Has anyone done this programmatically? The idea is that I will only have to maintain 1 project and any changes to that project will be propogated thru all other projects when the exes are rebuilt. I have toyed with changing name, key, homedir, etc in the pjx table but some items like menus appear to need adding thru the interface so their object code, etc are updated correctly in the pjx.
>
>Any help would be great! Thanks.