Results 1 to 4 of 4
  1. #1
    Join Date
    Dec 2004
    Location
    Madison, WI
    Posts
    3,926

    Unanswered: SQL Server relationships re-created in mdb Relational Diagram

    I use SQL Server linked tables in all my mdb applications. For one of these applications, I created a 2nd mdb with just the linked SQL Server tables in it (ie. no interface - so one of our data analysts could design their own queries.)



    Today she showed me that she had actually re-created all/most of the relationships for the SQL Server tables in the mdb Relational diagram (versus only creating the joins between the tables in the actual queries). She is the only one which uses this 2nd mdb.



    My question is would her creating relationships for the SQL Server tables in the mdb Relational Diagram (only the one she gets into) have any affect on other users using the main application? (and if so, I'm guessing it would only be when she has her mdb open.)



    She 'could' possibly have one of the relationships setup incorrectly in her mdb (I have yet to check). She does this to make setting up her queries easier since their are about 30 relational tables in the db.
    Expert Database Programming
    MSAccess since 1.0, SQL Server since 6.5, Visual Basic (5.0, 6.0)

  2. #2
    Join Date
    Mar 2009
    Posts
    5,442
    Provided Answers: 14
    If the main application the others are using is not based on the Access database your collegue used to build her own relational diagram I don't see how this could affect it, moreover if, as I supposed, you did not grant dbo privileges to any connection.

    This is off topic but why was it necessary to build queries in an Access database while a SQL Server database has stored procedures and views? Also, if it was necessary to work with an Access database using linked tables, I don't see why joins among the linked tables were not enough.
    Have a nice day!

  3. #3
    Join Date
    Dec 2004
    Location
    Madison, WI
    Posts
    3,926
    Thanks for the reply Sinndho,

    This db has a multitude of research data that can be queried in dozens and dozens of ways. For me, it would take all my time to design a stored procedure for each new way they wanted to look at the data.
    Expert Database Programming
    MSAccess since 1.0, SQL Server since 6.5, Visual Basic (5.0, 6.0)

  4. #4
    Join Date
    Mar 2009
    Posts
    5,442
    Provided Answers: 14
    Now that makes sense. Thanks for the answer pkstormy.
    Have a nice day!

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •