Charlotte Foust
cfoust at infostatsystems.com
Thu Jun 5 10:23:02 CDT 2003
By a "temporary relationship", I meant the joins you create in queries, not saved relationships. Charlotte Foust -----Original Message----- From: Gustav Brock [mailto:gustav at cactus.dk] Sent: Thursday, June 05, 2003 12:52 AM To: accessd at databaseadvisors.com Subject: Re: [AccessD] relations in which database Hi Bruce and Charlotte > "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." > AMEN! I don't get this. Relationships are primarily for defining referential integrity - a key part of database design - and as such they don't just "belong to the BE", they simply must exist there. As such you can retrieve or mirror them into any FE linking to that BE but that is just display of the relations and for use by the GUI query designer; it has no further use. By the way, what is a "temporary relationship"? If a new relationship is needed you are redesigning the database scheme and that must be implemented in the BE ... /gustav _______________________________________________ AccessD mailing list AccessD at databaseadvisors.com http://databaseadvisors.com/mailman/listinfo/accessd Website: http://www.databaseadvisors.com