A
aemAndy
I'm working with a database that has grown into a conglomerate catch-all
mishmash of veried functions. I'd like to de-centralize it into several
functional databases, so when someone supports this all the queries and
reports will be grouped properly. So, really, it's not separate databases as
much as still one database (data tables only in one location), but with
queries, and reporting split out into "children" databases. It's basically a
customer information management system -
#1 - All the data tables will still reside in the central database, with
links to the tables in all the decentralized functions. Let's call this
database "Central.mdb"
#2 - All regular, daily functions that interact with each other and update
the central data tables will remain on "Central.mdb"
#3 - All specialty functions that only happen a couple times a year, don't
update the central data tables, and actually pull together external data in
addition to calling on the central data tables I'd like to organize into
separate functional databases, again with links to the central data tables.
So, I have the main forms for navigating around the system, and from these
forms, you can call up the specialty reports at the click of a button for
that customer.
- So let's say I'm looking at customer who has [CustomerID]=15
- I want to call up their annual customer report, called rptCustomer,
passing the [Customer ID] variable to that generic report to filter it to
just that customer.
- But now I've moved all customer reporting functions to a separate
database, called 06Reps.mdb.
How do I, from my form on c:\database\Central.mdb click a button that will
- open the database c:\database\reporting\06.mdb
- open the report "rptCustomer" on that database
- pass the variable [CustomerID] along for filtering by the report
Please just let me know if this is possible or not, and how I'd structure
the command on the button click. There are a number of reasons why I feel it
needs to be structured this way.
mishmash of veried functions. I'd like to de-centralize it into several
functional databases, so when someone supports this all the queries and
reports will be grouped properly. So, really, it's not separate databases as
much as still one database (data tables only in one location), but with
queries, and reporting split out into "children" databases. It's basically a
customer information management system -
#1 - All the data tables will still reside in the central database, with
links to the tables in all the decentralized functions. Let's call this
database "Central.mdb"
#2 - All regular, daily functions that interact with each other and update
the central data tables will remain on "Central.mdb"
#3 - All specialty functions that only happen a couple times a year, don't
update the central data tables, and actually pull together external data in
addition to calling on the central data tables I'd like to organize into
separate functional databases, again with links to the central data tables.
So, I have the main forms for navigating around the system, and from these
forms, you can call up the specialty reports at the click of a button for
that customer.
- So let's say I'm looking at customer who has [CustomerID]=15
- I want to call up their annual customer report, called rptCustomer,
passing the [Customer ID] variable to that generic report to filter it to
just that customer.
- But now I've moved all customer reporting functions to a separate
database, called 06Reps.mdb.
How do I, from my form on c:\database\Central.mdb click a button that will
- open the database c:\database\reporting\06.mdb
- open the report "rptCustomer" on that database
- pass the variable [CustomerID] along for filtering by the report
Please just let me know if this is possible or not, and how I'd structure
the command on the button click. There are a number of reasons why I feel it
needs to be structured this way.