> Is there anything wrong with putting Data3 in its own backend database
(Backend2.mdb) and then linking both backends to the frontend and
setting any necessary relationships between the 2 backends in the
frontend?
If "necessary relationship" = "referentia l integrity" then referential
integrity may not be maintained if either backend database is opened
directly.
The backend will be unaware of the rules of the frontend; in fact, it
will be unaware of the existence of the frontend.
I had occasion when this happened to me in a FoxPro application (this is
one of the reasons I left FoxPro and came to JET). I THOUGHT coded RI
was impenetrable. But I didn't take into account a curious System
Administrator who had access to everything. In his playing with the db
he entered two school classes without schools. When we totalled things
up we got 1093 classes; actually there were 1091 classes. This could
have resulted in the improper authorization of the hiring of about three
full time equivalent staff at a cost of about $200 000; someone would
have caught hell about that, maybe me. The error was caught when we did
some spreadsheet analysis of another problem using the FoxPro data and
we noticed the anomaly.
Perhaps you will get advice on how to solve your problem in another way.
My first inclination would be to use MS-SQL, but that's right off the
top of my head and may not be appropriate at all for your situation.
--
--
Lyle
To subject an enemy belligerent to an unfair trial, to charge him with
an unrecognized crime, or to vent on him our retributive emotions only
antagonizes the enemy nation and hinders the reconciliation necessary to
a peaceful world.
Justice Frank Murphy
Yamashita v. Styer, 327 U.S. 1 (1946)
