Jim Lawrence
accessd at shaw.ca
Thu Sep 7 15:40:17 CDT 2006
Hi Thomas: The best way to accomplish this is to split the Access application into a FE and a BE. The BE hold the tables and the FE holds everything else. The BE would be made into a Master and Replicate and the data synchronized between the 2 either manually or automatically through a timed form. If this layout is used referential integrity of the BE mdb should not enter into it. HTH Jim -----Original Message----- From: accessd-bounces at databaseadvisors.com [mailto:accessd-bounces at databaseadvisors.com] On Behalf Of ewaldt at gdls.com Sent: Thursday, September 07, 2006 12:58 PM To: accessd at databaseadvisors.com Subject: [AccessD] Replication and Referential Integrity I've created a database that is used by two companies. For purposes of security, it cannot be on a network drive shared by the two companies. More detail isn't really necessary. What it amounts to is that only one company can use it at a time. I have had replication suggested to me. I know what it is, of course, but have only played with it on a very minor and experimental basis. However, the individual who recommended it to me is more experienced with it, and he said that it cannot be used with a database that employs referential integrity. Is he correct? I am sure that he knows more than I do about replication, but that doesn't mean much. TIA. Thomas F. Ewald FCS Database Manager General Dynamics Land Systems (586) 276-1256 This is an e-mail from General Dynamics Land Systems. It is for the intended recipient only and may contain confidential and privileged information. No one else may read, print, store, copy, forward or act in reliance on it or its attachments. If you are not the intended recipient, please return this message to the sender and delete the message and any attachments from your computer. Your cooperation is appreciated. -- AccessD mailing list AccessD at databaseadvisors.com http://databaseadvisors.com/mailman/listinfo/accessd Website: http://www.databaseadvisors.com