If this is your first visit, be sure to check out the FAQ by clicking the link above. You may have to register before you can post: click the register link above to proceed. To start viewing messages, select the forum that you want to visit from the selection below. |
|
|
Thread Tools | Display Modes |
#1
|
|||
|
|||
Enforcing ref. integrity between MDB files
Greetings from Canada.
This may sound like a stupid question. Is it possible to enforce referential integrity between tables stored in two separate Access MDB files? For example, I have tables in database #1 that contain spatial information. One of these tables is called SITE. In database #2 I have a SAMPLE table that I wish to join to the SITE table in database #1 and enforce referential integrity (cascade update only). Database #1 is a "geodatabase" used by GIS software, but is actually a MDB file that can be opened and edited in Access. I am only able to join the tables (the SITE_ID field is common to both tables), but the referential integrity options are dimmed out. Is there a way around this? Thanks in advance. Sincerely, Dirk Winnipeg, Canada |
#2
|
|||
|
|||
Enforcing ref. integrity between MDB files
The simple answer is no, you cannot.
-- Regards, Adrian Jansen J & K MicroSystems Microcomputer solutions for industrial control "Dirk" wrote in message ... Greetings from Canada. This may sound like a stupid question. Is it possible to enforce referential integrity between tables stored in two separate Access MDB files? For example, I have tables in database #1 that contain spatial information. One of these tables is called SITE. In database #2 I have a SAMPLE table that I wish to join to the SITE table in database #1 and enforce referential integrity (cascade update only). Database #1 is a "geodatabase" used by GIS software, but is actually a MDB file that can be opened and edited in Access. I am only able to join the tables (the SITE_ID field is common to both tables), but the referential integrity options are dimmed out. Is there a way around this? Thanks in advance. Sincerely, Dirk Winnipeg, Canada |
#3
|
|||
|
|||
Enforcing ref. integrity between MDB files
It's not possible.
-- Doug Steele, Microsoft Access MVP http://I.Am/DougSteele (no e-mails, please!) "Dirk" wrote in message ... Greetings from Canada. This may sound like a stupid question. Is it possible to enforce referential integrity between tables stored in two separate Access MDB files? For example, I have tables in database #1 that contain spatial information. One of these tables is called SITE. In database #2 I have a SAMPLE table that I wish to join to the SITE table in database #1 and enforce referential integrity (cascade update only). Database #1 is a "geodatabase" used by GIS software, but is actually a MDB file that can be opened and edited in Access. I am only able to join the tables (the SITE_ID field is common to both tables), but the referential integrity options are dimmed out. Is there a way around this? Thanks in advance. Sincerely, Dirk Winnipeg, Canada |
#4
|
|||
|
|||
Enforcing ref. integrity between MDB files
On Tue, 8 Jun 2004 14:02:56 -0700, "Dirk"
wrote: Is it possible to enforce referential integrity between tables stored in two separate Access MDB files? As noted, the answer is a flat No. The reason is pretty clear if you think about it: if you have a relational constraint defined in ABC.MDB on a pair of tables from ABC.MDB and XYZ.MDB, there is nothing to prevent someone from opening XYZ.MDB directly (or from QRS.MDB) and making a change to the data which violates that constraint. Since ABC.MDB isn't even open it is powerless to enforce the constraint. John W. Vinson[MVP] Come for live chats every Tuesday and Thursday http://go.compuserve.com/msdevapps?loc=us&access=public |
Thread Tools | |
Display Modes | |
|
|