How to know when to start a new Database

[brharrii]

I built a product spec database.
- Forms, Queries and reports are all managed by me.
- stores a record of each product we create


- allows new products to be added as time goes on
- Prints reports to ensure compliance with specifications
- approximately 1000 records, will probably continue to grow


Now I need to build a database that will be used to record quality assurance checks on the same products from the product spec database.

- forms will be used by our QA department to enter results of daily QA checks
- primarily used for data entry and trend analysis.
- will add a few hundred records each day
- needs a few fields from the Product Spec database to perform weight calculations.

I'm trying to decide if I should create a completely new database or just add more tables / forms/ reports to the one I already have. I worry a little bit about the database getting too big and un manageable, but wanted to get a some thoughts before I went one way or the other.

Thanks

Bruce

[June7]

Number of records is not limiting factor, file size is. Access file size is limited to 2gb. I have a split database with FE of 43mb and BE of 130mb.

Design edits cause file size to bloat. Run Compact & Repair periodically, especially after extensive edits.

[pbaldy]

Generally if the functionality is similar, I'd put it in the same db, if it's different I'd create a new one that linked to the data table in the first. You don't want to maintain the same data in two places.