Hello,
I created an Access database that Project Managers use to track and manage their Construction Projects. I eventually installed SQL Server and used the Access 2010 Upsizing Wizard to put the individual databases on it – I create a new database for each new Project from a master template, nothing changes about the structure. I am in the process of redesigning this database and I want to have all projects in one database on SQL Server and create front ends in Access for the individual users, pulling only their Project information.
Right now there is an individual SQL Database for each Project so there are around 20+ databases, each with the same tables. Some of the tables contain the same data across all Projects (e.g. Employees, SubcontractorContacts), but because they are each in their own database, if information gets updated in one, it doesn’t translate to the others. Other tables, however, contain data specific to the particular Project (e.g. RFIs, Letters). ProjectNumber is the PK in the ProjectInfo table and it is a FK in the other tables. If I create one Master Project Database in SQL Server and create Access front ends pulling only records for whichever Project the user is managing, will the front ends be slowed way down by the increase of records in the SQL Database? They would only see records for their Project, but the database from which their records would be pulling would contain all records for all Projects. Is it better to keep only the tables with the same data across all Project databases in one database and link it to the front ends, but still create a new SQL Database for each Project? It is a lot of data and I do not want to sacrifice speed.
I appreciate your suggestions.
Betsy