S
SK
Greetings,
Just a general question on DB design(For Access 2000). I
have read a lot about the benefits of splitting a DB into
Fron-end and back-end and like that approach. However, I
want to know if I can do the same in my situation:
I am dealing with a number of databases here(10-15).
There are several tables(15 or so) which are common to
almost all of these databases. However, most of these
databases have specific tables(varying from 0 - 5 per
database), queries, Forms, reports, modules, etc..
So I have thought of creating a Common(or Central) DB
which will house all the common tables. At the same time
I will have other DBs which link to the central DB but
also have tables, Forms, queries,reports, etc. which are
pertaining to that database. Benefits of this are:
- Users will not have to maintain only one set of tables.
- I do not have a huge single DB
- N/w traffic will be less
- Maintenance will be easier.....
In this way, I will have a Central DB and x number of
other databases which link to this Central DB.
My Questions:
1. Is this the best design approach that will not
prohibit me from using other Access features?
2. I am using relationships in each DB but I think that I
cannot build a relationship between a linked table(i.e. a
table not present in current DB) and a table that is
present in current. Please advise if this can be done as
it will save me a lot of time where I am writing VBA code
to validate data before updating data in several tables.
3. How will I be able to get the benefit of Front-end and
back-end approach in my situation?
I have applied Workgroup security to these databases,
created modules(usng ADO) and done several other good
things. My aim is to make these databases work as multi-
user secured DBs.
Please advise.
Thanks in advance.
SK
Just a general question on DB design(For Access 2000). I
have read a lot about the benefits of splitting a DB into
Fron-end and back-end and like that approach. However, I
want to know if I can do the same in my situation:
I am dealing with a number of databases here(10-15).
There are several tables(15 or so) which are common to
almost all of these databases. However, most of these
databases have specific tables(varying from 0 - 5 per
database), queries, Forms, reports, modules, etc..
So I have thought of creating a Common(or Central) DB
which will house all the common tables. At the same time
I will have other DBs which link to the central DB but
also have tables, Forms, queries,reports, etc. which are
pertaining to that database. Benefits of this are:
- Users will not have to maintain only one set of tables.
- I do not have a huge single DB
- N/w traffic will be less
- Maintenance will be easier.....
In this way, I will have a Central DB and x number of
other databases which link to this Central DB.
My Questions:
1. Is this the best design approach that will not
prohibit me from using other Access features?
2. I am using relationships in each DB but I think that I
cannot build a relationship between a linked table(i.e. a
table not present in current DB) and a table that is
present in current. Please advise if this can be done as
it will save me a lot of time where I am writing VBA code
to validate data before updating data in several tables.
3. How will I be able to get the benefit of Front-end and
back-end approach in my situation?
I have applied Workgroup security to these databases,
created modules(usng ADO) and done several other good
things. My aim is to make these databases work as multi-
user secured DBs.
Please advise.
Thanks in advance.
SK