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" <tas1234@yahoo.com> wrote in message
news:bedcdd7b.0309261259.24510514@posting.google.c om...[color=blue]
> 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[/color]
