>Hello,
>
>Our company has sold a complete business software package for the last 15 years to Music Retailers. It up until now has been written in a Dos RDBMS called Powerflex. There are many different modules to this package (A/R, A/P, Rentals, Lessons, Repair, Inventory, P/O, G/L, etc). My first project while trying to learn Foxpro was to write the Lesson Module which I did and it works great thanks to a lot of help from you here on the UT. Let me preface my next question by saying our intent is to develop a few of these modules to sell stand alone as well as incorporate into an overall package for the music retailer. For example we can sell the Lesson Scheduler to Piano teachers and maybe sell the repair module to small instrument repair shops stand alone, but I also need to incorporate these modules into one large package to sell to music stores who have all of these departments.
>
>My question is would I create a separate database for each module? Certain tables will need to be accessed by more than one module ie(inventory table, customer table, "gl detail" table) so how would I handle this?
>

Hi Paul,

We have faced exactly the same problem (different industry <g>). We have decided on a single DBC. I can't think of a good reason not to do so.

Although each of our modules can be a standalone app, the real power is in the integration between modules which cries out for sharing of data.

Hope this helps,

Ken