Advertisement

05.21.2008 at 12:21PM PDT, ID: 23422157
[x]
Attachment Details
[x]
The Solution Rating System

With so many solutions, how can you tell which solutions are most likely to help you and which ones are not? To provide you with a tool to use, we rate our solutions based on various elements that most accurately determine if a solution is a quality solution. To explain what factors affect the solution rating, here are the elements we take into consideration when formulating our solution rating.

  • The Grade of the Solution
  • The Zone Rank of the Expert Providing the Solution
  • The Number of Author and Expert Comments
  • The Number of Experts Contributing
  • The Feedback of the Community

Your Input Matters
Because of the way the system is set up, the most important variable in this equation is you. As a member of Experts Exchange, you are able to cast your vote on the quality of the solutions in regard to how complete, accurate, helpful and easy to understand each solution is. When you provide your feedback, each rating is adjusted accordingly. So, if you see a solution that has a poor rating that you think is a good solution, let us know by rating it. As you do, the rating will be adjusted and will become more accurate for other members of our site.

If you have any suggestions that you would like to make for our rating system, please ask a question in the Suggestions Zone of Community Support.

Thank you!

9.0

Relationships in between multiple databases, linked tables

Asked by dyoung520 in Access Architecture/Design, Access Coding/Macros

Tags: , , ,

I have a database frontend and backend in access 2000.  The frontend uses tables from 3 other backend access databases.  I am working on delete routines for certain records.

My question is how (where) the relationships for a setup like this should be handled.  Should I be relying on cascade delete relations.  If that is the case I am confused on how to define these between the databases.

My frontend has all the relations defined, but has grayed out boxes for the options (e.g. cascade delete, etc.).

Should this simply be handled with code - fine by me?  Just want to make sure I am doing this the "right" way.

Thanks!!

Start Free Trial
 
 
[+][-]05.21.2008 at 12:30PM PDT, ID: 21618249

At Experts Exchange, members can ask their questions to thousands of technology professionals, also known as Experts. Experts compete and collaborate to answer those questions by leaving comments like this one.

Start your 7-day free trial to view this Expert Comment or ask the Experts your question.

 
[+][-]05.21.2008 at 12:40PM PDT, ID: 21618334

View this solution now by starting your 7-day free trial. Setting up your free trial is quick, easy, and secure. We will return you to this solution, unlocked, when you're done.

 

About this solution

Zones: Access Architecture/Design, Access Coding/Macros
Tags: Microsoft, Access 2000, 2000, VBA
Sign Up Now!
Solution Provided By: jimhorn
Participating Experts: 2
Solution Grade: B
 
 
 
Loading Advertisement...
20080716-EE-VQP-32 / EE_QW_2_20070628