Charlotte Foust
cfoust at infostatsystems.com
Wed Jun 4 10:27:21 CDT 2003
Relationships do not have to reside in the BE. However, you can only enforce referential integrity between tables in the same database unless you want to do a lot of coding to create the Access/Jet equivalent of triggers. The best arguments for putting relationships in the back end is 1) You can create any kind of temporary relationship you want in the front end on the fly as you need it. They don't have to be stored there, and 2) If you front end becomes toast, you still have the relationships in the back end where they belong. Charlotte Foust -----Original Message----- From: Marcel Vreuls [mailto:marcel.vreuls at oop.nl] Sent: Wednesday, June 04, 2003 5:27 AM To: accessd at databaseadvisors.com Subject: RE: [AccessD] relations in which database Gustav, And what if I have four BE with different tables that have to be related to each other. The only solution is the releationships in the FE? or am i missing something. Why do you think it won't work? Gr Marcel -----Original Message----- From: accessd-bounces at databaseadvisors.com [mailto:accessd-bounces at databaseadvisors.com]On Behalf Of Gustav Brock Sent: woensdag 4 juni 2003 15:13 To: accessd at databaseadvisors.com Subject: Re: [AccessD] relations in which database Hi Marcel The main disadvantage is that it won't work. As Charles wrote, relations have to reside in the backend. Sometimes relations increase speed. If Excel users should access the BE, relations can make this safe. If not, create queries they can and must use. If you need to adjust relations, open the BE exclusively and perform the changes and close. /gustav > I am stugling with the following. In our current situation I have a FE > and a > BE database. The relationships are currently stored in the BE > database. Now > the question is why not put them in the FE database and just leave the plain > tables in the be database. > Advantages should be > - performance in multiuser env. > - more control over the database because with each update you can > change, add a relationship > - peoplo who want to access the database through excel, and so on have more > trouble in comprending the database. > - field updates, new tables are easily to create instead of using 3rd party > backend updaters > Are there disadvantages??? _______________________________________________ AccessD mailing list AccessD at databaseadvisors.com http://databaseadvisors.com/mailman/listinfo/accessd Website: http://www.databaseadvisors.com _______________________________________________ AccessD mailing list AccessD at databaseadvisors.com http://databaseadvisors.com/mailman/listinfo/accessd Website: http://www.databaseadvisors.com