Thanks Hilmar. Actually I have a requirement where even though clients want one or both, there are customization to the screens & reports which is something only they like. I such a case I was hoping to develop a basic application for all and start from there when a job arrived.

Any suggestion, first hand experience in such a case?


>>Hi all
>>
>>I develop customized solutions for clients. Thus I end up with different jobs many of them based on Accounting and Inventory. There will be some odd jobs, yes.
>>
>>Now that I have converted my self from FPD to VFP I would like to know how to go about generating projects for Accounting another for Inventory and when required subclass them (few clients want only accounting, only inventory and few want both)
>>
>>Is it possible to tackle such a development effort. Becuase of OOP I guess any updates I do to the Accounting module should reflect to other projects as and when deployed.
>>
>>What will be my responsibilities for sync table fields for such modules?
>>
>>Please clarify my expectations from VFP.
>
>I don't see how subclassing could help here. It seems much simpler to create a combined accounting & inventory system, and then disable or hide individual items, depending on some condition. The condition might be a compile-time constant (#DEFINE).
>
>If you want to keep your executable smaller, you might try to keep class libraries separate, and then have three versions of the executable (accounting, inventory, both), that include only the forms and classes that are of interest in each case.
>
>HTH,
>
>Hilmar.