Consolidate Tables Into One File.
The company that I work for has developed five databases over the last ten years.
All of the databases are split, with the backends residing in the same folder on a network drive.
Some of the backend files are .mdb, others are .accdb.
There is a frontend for each backend, but each of the frontends has links to more than one backends.
Would there be any advantage to consolidating all of the tables into one backend file? Any downside to doing the consolidation?
Thank you for taking the time to report an issue.
What's wrong... Please write below.
What I would like to do is filter in the main union query all records that are 2011 or 2012 only.
This is what I have:
I have the same field in 2 tables. Each table has data in the field, but the data in each table is for different dates. In the main table, the field was used through 2001, and then someone created a new table for this field. They didn't remove the old field, or move the data to the new field. The old dates only exist in the old table, the newer dates are in both tables, but only have data for this field in the newer table.
Is there a simple way to consolidate the data from the two fields? I want all the data to be in the new table.
As an example, two tables of data. The first table is "tbl ONE" and the second "tbl TWO". Each table has a Field called [Data]. I want to create a new table that amalgamates the [Data] field info from both tables but also creates a new Field, [SourceTable}, that records which table the data originated. So structure of the Amalgamated table is [Data], [SourceTable].
Is there a way to do this using by creating a function and using select case? I'm not sure how to reference multiple fields in a table.
Here is an example of what I was originally thinking of...
So within Form_Open I have:
Run-time error '2485':
Microsoft Office Access cannot find the macro 'Consolidated'
I would now like to combine them into one overall application.
Can I set up the main form to select the application you need to work with.
Set the relationships to all the tables in all applications .
For instance in app A request a report from app B with out going back to the main form and running app B.
If this can be done is there a limit on the number of tables that an app can have
My other idea was to consolidate all tables into one and just having a column that specifies what type of Object it is. The problem is that there is such a wide variety of properties each table has that I'll exceed the limit of how many columns you can have in a table.
What's the best design approach for this situation?
Essentially, I want to be able to save the data from the original database and start a new database (file) with all of the lookup tables intact, but a clean set of data entry tables.