Split database (single front end w/ multiple backends)

[Therese A. Sorna]

Hello all...

I am trying to develop a database that could be duplicated many times
over with different data (separated by project) in each database, but
the same front end information. I was wondering if anyone knew of a
way to have multiple backends and just one front end, to ease updates.

Thanks,
Therese

[MacDermott]

Check at http://www.mvps.org/access/tables/tbl0009.htm for ideas on how to
point the table links in your database to a different back end.

HTH
- Turtle

"Therese A. Sorna" <ta*****@yahoo. com> wrote in message
news:be******** *************** ***@posting.goo gle.com...

Hello all...

I am trying to develop a database that could be duplicated many times
over with different data (separated by project) in each database, but
the same front end information. I was wondering if anyone knew of a
way to have multiple backends and just one front end, to ease updates.

Thanks,
Therese

[Larry Linson]

Except in very unusual circumstances, it is simpler and easier if you put
all the information in one back-end database, with the records identified by
project. One of the unusual circumstances might be where you keep data for
different clients, the clients also have access, and the data is "company
confidential".

It's likely, if there aren't some unusual circumstances, that one day you
might want to do some comparative analysis, and that will be far easier if
you have all the information in one database.

If you can't combine the data, you've had one reference on code to select
and relink tables. Another will be found in the Solutions.MDB sample
database from Microsoft -- it comes on the install disks with Access 97 and
earlier, and will be installed in the Samples subfolder of the Office folder
of the folder hierarchy where you installed Office or Access; for Access
2000 and later, download from
http://msdn.microsoft.com/library/en...ml/bap2000.exe. It's not
for exactly the purpose you describe, but it'll be easy to adapt the code.

Larry Linson
Microsoft Access MVP

Larry Linson
Microsoft Access MVP
"Therese A. Sorna" <ta*****@yahoo. com> wrote in message
news:be******** *************** ***@posting.goo gle.com...

Hello all...

I am trying to develop a database that could be duplicated many times
over with different data (separated by project) in each database, but
the same front end information. I was wondering if anyone knew of a
way to have multiple backends and just one front end, to ease updates.

Thanks,
Therese

[David W. Fenton]

ta*****@yahoo.c om (Therese A. Sorna) wrote in
<be************ **************@ posting.google. com>:

I am trying to develop a database that could be duplicated many
times over with different data (separated by project) in each
database, but the same front end information. I was wondering if
anyone knew of a way to have multiple backends and just one front
end, to ease updates.

Years ago, I had a client who was a management company that ran 25
or so parking garages in NYC. They had an old dBase II program that
had separate data files for each garage. When I built a replacement
Access application, I put all the garages in one MDB and simply put
a GarageID in the Customer table (the top-level table). I then made
choosing the Garage the first step in opening the application, but
also allowed them to choose ALL GARAGES.

If the projects have the exact same data structure (and they must
if a single front end can be used for all of them), then include a
table for Projects and put a ProjectID in the table at the top of
your data structure. In the long run, you will be glad you did it.

--
David W. Fenton http://www.bway.net/~dfenton
dfenton at bway dot net http://www.bway.net/~dfassoc