I think that it is better to hold all the modules in single DBC what I usually do is sperate other things into other DBCs liek a SYSTEM DBC, for user right,users,keys etc. and a USER DBC per use on the local for user queries etc. Arnon > >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? > >My initial thought is to create one A/R database that would hold the inventory, customer and gl tables, for example, and then create separate dbc's for each of the other modules. So then, for example Entering a repair ticket would need to open the a/r dbc to get the customer info? > >Or maybe its better to just create one dbc? > >If you also could shed light as to whether each dbc or module would be in its own directory or is it normal to have multiple dbc's in one main application directory. > >I hope this all makes sense....thanks for your consideration. > >Paul