From: Irene_58 on 10 Feb 2010 13:50 Hi, I have 3 or 4 databases developed separarely over the past couple of years covering different areas of company activities - project monitoring, support call monitoring, QHSE monitoring etc. The company has grown and I'm looking to consolidate and distribute these. I'd intended to split them into FE/BE so that the just the appropriate FEs could be installed on any user's PC and the back-ends would reside on the server. I'd thought at first that I could have a "core" BE with e.g. a staff and client table and activity specific BEs. But the activity tables have the core tables PKs as FKs. Does this mean I have to put all the tables into 1 BE? or am I missing something? -- Irene
From: Steve on 10 Feb 2010 14:25 Yes, 1 BE. You want to do that anyway so you can create queries, forms and reports across multiple activities. Steve santus(a)penn.com "Irene_58" <Irene58(a)discussions.microsoft.com> wrote in message news:A7A94706-39A9-4BFF-AA18-15D20BFC4B52(a)microsoft.com... > Hi, > I have 3 or 4 databases developed separarely over the past couple of years > covering different areas of company activities - project monitoring, > support > call monitoring, QHSE monitoring etc. The company has grown and I'm > looking > to consolidate and distribute these. I'd intended to split them into > FE/BE > so that the just the appropriate FEs could be installed on any user's PC > and > the back-ends would reside on the server. I'd thought at first that I > could > have a "core" BE with e.g. a staff and client table and activity specific > BEs. But the activity tables have the core tables PKs as FKs. Does this > mean I have to put all the tables into 1 BE? or am I missing something? > -- > Irene
From: Jeff Boyce on 10 Feb 2010 15:37 Irene If you haven't gotten a response yet covering your question about PKs and FKs, here's some thoughts... If you are saying that each of your (3 or 4) databases have "core" tables, and those cores are the same topics, but the data in each "core" table is different, from app to app, then yes, you have a potential issue in connecting the core records with their respective child table records. For example, if all dbs have a core tblPerson table, but App1 has John Doe as PersonID=1, while App2 has Bill Smith as PersonID=1, and so on, then you clearly cannot expect the non-core tables that point to tblPerson to have the correct foreign keys (most of the time). I guess I'm having trouble visualizing what you mean by "the activity tables have the core tables PKs as FKs". Is that the same as saying that the activity tables are your "child" tables? More info, please... Regards Jeff Boyce Microsoft Access MVP -- Disclaimer: This author may have received products and services mentioned in this post. Mention and/or description of a product or service herein does not constitute endorsement thereof. Any code or pseudocode included in this post is offered "as is", with no guarantee as to suitability. You can thank the FTC of the USA for making this disclaimer possible/necessary. "Irene_58" <Irene58(a)discussions.microsoft.com> wrote in message news:A7A94706-39A9-4BFF-AA18-15D20BFC4B52(a)microsoft.com... > Hi, > I have 3 or 4 databases developed separarely over the past couple of years > covering different areas of company activities - project monitoring, > support > call monitoring, QHSE monitoring etc. The company has grown and I'm > looking > to consolidate and distribute these. I'd intended to split them into > FE/BE > so that the just the appropriate FEs could be installed on any user's PC > and > the back-ends would reside on the server. I'd thought at first that I > could > have a "core" BE with e.g. a staff and client table and activity specific > BEs. But the activity tables have the core tables PKs as FKs. Does this > mean I have to put all the tables into 1 BE? or am I missing something? > -- > Irene
From: John W. Vinson on 10 Feb 2010 16:15 On Wed, 10 Feb 2010 10:50:01 -0800, Irene_58 <Irene58(a)discussions.microsoft.com> wrote: >Hi, >I have 3 or 4 databases developed separarely over the past couple of years >covering different areas of company activities - project monitoring, support >call monitoring, QHSE monitoring etc. The company has grown and I'm looking >to consolidate and distribute these. I'd intended to split them into FE/BE >so that the just the appropriate FEs could be installed on any user's PC and >the back-ends would reside on the server. I'd thought at first that I could >have a "core" BE with e.g. a staff and client table and activity specific >BEs. But the activity tables have the core tables PKs as FKs. Does this >mean I have to put all the tables into 1 BE? or am I missing something? I think the nub of your problem is - as you have evidently gathered - that Relationships with referential integrity enforced can only be established between tables in the same backend. Unless there is some very good reason to do otherwise (such as the size of the backend approaching the 2GByte limit, or really critical security issues) I'd use a single backend; although you can create queries joining tables across two backends, performance will suffer. And you *do* lose referential integrity. You might want to look into SQL Server Express as a shared backend. -- John W. Vinson [MVP]
From: Stop$teve on 10 Feb 2010 16:13
"Steve" <notmyemail(a)address.com> schreef in bericht news:ehWGMboqKHA.5940(a)TK2MSFTNGP02.phx.gbl... > Yes, 1 BE. You want to do that anyway so you can create queries, forms and reports across multiple activities. > It depends $teve... but... Get lost $teve. Go away... far away.... No-one wants you here... no-one needs you here... OP look at http://home.tiscali.nl/arracom/whoissteve.html (Website has been updated and has a new 'look'... we have passed 11.000 pageloads... it's a shame !!) For those who don't 'agree' with this mail , because $teve was 'helping' with his post... We warned him a thousand times... Sad, but he is not willing to stop advertising... He is just toying with these groups... advertising like hell... on and on... for years... oh yes... and sometimes he answers questions... indeed... and sometimes good souls here give him credit for that... ==> We are totally 'finished' with $teve now... ==> Killfile 'StopThisAdvertising' and you won't see these mails.... Arno R |