While I would generaly agree with Rick's commentary, I think it aplies to individuals who actually use the capabilities of the relations available in Ms. Access. From the question itself, it is aparent that you are not using the relationships. Therefore some of his points simply do not apply. In many situations, there CAN be reasons to segregate the tables in a databse to more than one actual (physical) database. Rick has mentioned a few, I could add a few, and I am sure that the 'community' could pile on many additional examples.
Personally, I would offer two general thoughts. First, if you are going to use a relational database, the use the inherent capabilities to your advantage. This, in general, includes the RELATIONSHIPS, such that cascade effecs are implemented. This can be daunting - at first. You will end up with unexpected errors when you attempt some operations in opposition to the defined relationships. They will be perplexing and frustrating. You will get over it, to find that many of the features save a considerable amount of time/effort in maintaining the database.
Second. Most databses are simply 'state models' of real world processes or functions. The various tables are simply stored states of different instances of the model. So, look at the 'real world' function you are modeling in the database. If - in that world - the model SHOULD be seperated, then you database PROBABLY should be seperated. If, on the otherhand, your real worl function is integrated, then your database PROBABLY should remain integrated. Ask the question. Does this part exist without the other part? Can ther be any orders without the customers? Will there be any orders without the customers? Are there VALID relationships between orders and sales (or customers) which need to be enforced?
Be careful. Some of these are NOT what they appear to be. Some of them change between situations. For instance, a wholesaler would usually NOT want to commit to the sale of merchandise which is not it stock, thus inventory and sales NEED to be tied together in a relationship. A retailer, on the other hand, would look VERY foolish if the Point of sale system refused to accept the sale of an item because the inventory system should none in stock.
MichaelRed
redmsp@erols.com
There is never time to do it right but there is always time to do it over