RE: [KCFusion] system intergration

[Templin, Luke]

In Sql Server there's a facility called "Linked Servers" that will allow you to share data across databases. The documentation is fairly lengthy so you would be best off to get the SQL SERVER Books online to get all the details.   It seems like you're planning a workaround with code that might better be addressed as a single database application with three apps running off the same datasource. Of course I work in a place where there are 168 databases instead of the 1 that should be present.     -----Original Message----- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]On Behalf Of Adaryl Wakefield Sent: Tuesday, December 02, 2003 12:48 PM To: [EMAIL PROTECTED] Subject: Re: [KCFusion] system intergration Oh sorry i always forget this   SQL Server 2k Win 2k server CF 5   Adaryl Wakefield Aviator by passion Programmer by sheer force of will ----- Original Message ----- From: Templin, Luke To: [EMAIL PROTECTED] Sent: Tuesday, December 02, 2003 12:40 PM Subject: RE: [KCFusion] system intergration What database are you using? Oracle does let you connect and access tables in another db. MS Access also has similar functionality  -----Original Message----- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]On Behalf Of Adaryl Wakefield Sent: Tuesday, December 02, 2003 12:35 PM To: [EMAIL PROTECTED] Subject: [KCFusion] system intergration I was just curious how someone with more experience would do this.   I have three applications that run off three different databases. Which means three differnet passwords, three different logins yadda yadda yadda. Im in the middle of creating a system where everything is controlled by one username and password set. Im doing this by taking the three primary parent tables (is that even the correct term?) and combining common attributes. What remains of the primary parent tables of the three applications after stripping out common attributes will become conceputally child tables to the super table. The super table will be moved into another database making that 4 total. Here is what im thinking. You cant join tables accross databases so what I was thinking was holding the primary key of the super table in a session var to join the three "child" tables. Like   test1 DB members(memberID PK, firstName, lastName)   test2 DB organizations(orgNum PK, memberID FK)   <cfquery name="foo" datasource="test2"> SELECT orgName FROM organizations WHERE orgNum = #session.memberID# </cfquery> <!---Just pretend the lock is there--->   Thoughts? Ridicule?   Adaryl Wakefield Aviator by passion Programmer by sheer force of will