Re: Fixing Relationship on back-end DB
- From: OldPro <rrosskopf@xxxxxxxxxxxxx>
- Date: Wed, 31 Oct 2007 06:11:42 -0700
On Oct 31, 7:30 am, "paii, Ron" <n...@xxxxxx> wrote:
I have an application that has been built and expanded for over 10 years. As
modules have been added to the front-end, new back-end DBs have been
created. For example the back-end DBs for Inventory, Purchase order, Work
Order all exist in separate MDBs. This of course eliminates the ability to
create relationships between each of the back-ends, so referral integrity
between the back-ends is maintained in the front-end forms.
Now I am trying to fix this error in design. My 1st step was to create a new
backend database and import all the tables from the other back-ends. then
create relationships with referral integrity. I was surprised by how few
orphaned records existed :). My problem, Access is reporting a limit on the
number of indexes as I turn on more referral integrity. Is there a
historical limit on indexes like controls on a form? Or will I need to
restructure the database to reduce the number of child tables referencing
parent tables.
I was hoping to combine the MDBs without making any major changes to the
table structure. When done, I want to test the existing front-end on the new
back-end.
I've never heard of a limit on indexes... how many do you have?
.
- Follow-Ups:
- Re: Fixing Relationship on back-end DB
- From: OldPro
- Re: Fixing Relationship on back-end DB
- References:
- Fixing Relationship on back-end DB
- From: paii, Ron
- Fixing Relationship on back-end DB
- Prev by Date: FileMaker vs. Access
- Next by Date: Re: Fixing Relationship on back-end DB
- Previous by thread: Fixing Relationship on back-end DB
- Next by thread: Re: Fixing Relationship on back-end DB
- Index(es):
Relevant Pages
|
|
