Access Database looking for tables location

[German Saer]

I developed an application in access for a company that has some divisions.
Each division doesn't have any relation to another. The whole thing is done
with the exception of ...: (I Explain)...
The database is splitted in "1 Database" which has the forms and reports and
"several databases" for tables only with the same structure all of them.
They are like copies of the same. All I need is to tell the database that
contains the forms depending on where the application is running connect to
a different database of tables.
The application is only one for everybody which manage the same structure of
data but different data. For example:

C:\My Docs\Application.mdb

C:\My Docs\Division1.mdb
C:\My Docs\Division2.mdb
C:\My Docs\Division3.mdb

Once I open the database "Application" how do I connected to Division1.mdb
data instead to be attached to Division2.mdb. I made a SignOn Form and
depending of the user it has to attached to one of the divisions.

PD: All Divisions Databases has the same tables with the same structure.
Just different data.

Thanks in advance,

German Saer
(e-mail address removed)
Orlando, FL

 

[Mike Painter]

I developed an application in access for a company that has some divisions.
Each division doesn't have any relation to another. The whole thing is done
with the exception of ...: (I Explain)...
The database is splitted in "1 Database" which has the forms and reports and
"several databases" for tables only with the same structure all of them.
They are like copies of the same. All I need is to tell the database that
contains the forms depending on where the application is running connect to
a different database of tables.
The application is only one for everybody which manage the same structure of
data but different data. For example:

C:\My Docs\Application.mdb

C:\My Docs\Division1.mdb
C:\My Docs\Division2.mdb
C:\My Docs\Division3.mdb

Once I open the database "Application" how do I connected to Division1.mdb
data instead to be attached to Division2.mdb. I made a SignOn Form and
depending of the user it has to attached to one of the divisions.

PD: All Divisions Databases has the same tables with the same structure.
Just different data.

If all the data tables have the same structure then good relational design
would expect only one table of each type.
It will solve problems now, make any changes in the future much easier and
almost certainly solve big problems in the future.
All you need do, assuming the other relationships are valid is add one
"Division" field to a table.

If you insist on doing it your way then you will have to link all the other
databases and write code *everywhere* to set the recordsource for the
various forms and reports.

 

[JohnFol]

You could base the db on select statements (or queries that have the
querydef changed at run time.

For example

SELECT CustomerID
FROM Customers
IN C:\My Docs\Division1.mdb
WHERE CustomerID Like "A*";