Kevin,

I would like to compare notes with others to iron out the details

Thanks

Rex


>Rex,
>
>>I am developing an accounting system for a client that I would like to be able to distribute (and sell) in modules (Payroll, GL, Billing, AR, etc). I am just looking for design ideas so I don't spend all my time trying to modularize the subsystems. Do I create separate apps for each module? How do I tie the apps together? I have some ideas on the subject, but I was just wanting to pick the brains of the MM community so I don't have to reinvent the wheel.>
>
>Sounds interesting...I've had a few people who have asked about this very thing. If you'd like, I may be able to put you in touch with them...it would be nice if you had some requirements up front so that you could create something that is flexible enough to be sold to a wider market.
>
>ANYWAY, you can use the application created by QuickStart as the "main" program. You can then create a different project for each module (payroll.pjx, gl.pjx, billing.pjx, etc.). These projects can simply contain the classes / program files that are specific to the module. You can then use the Abstract Factory from within the main application to instantiate the objects from the classes in these external files as the user runs forms / processes in a given module.
>
>Regards,