Welcome to SPN

Register and Join the most happening forum of Sikh community & intellectuals from around the world.

Sign Up Now!

Efficiency question

Discussion in 'Information Technology' started by Eric @ CMN, Evansville, Nov 4, 2005.

  1. Eric @ CMN, Evansville

    Eric @ CMN, Evansville
    Expand Collapse
    Guest

    Is it more efficient to have a rather complex, single query based on several
    tables, or have a fairly simply query that is based on several other simple
    queries that are ultimately based on single tables each ?

    I'm inheriting a database application that just seems to me to be of a
    rather inefficient design. Any thoughts on efficiency and speed would be
    appreciated.....by the way, this will become a shared database being run on a
    network.

    Thanks !
     
  2. Loading...

    Similar Threads Forum Date
    Sikh News Punjab on war footing for 100% energy efficiency in households (Express India) Breaking News Aug 29, 2008
    Question About GGS Questions and Answers Aug 28, 2016
    Marriage And Discrimination Related Questions Blogs Mar 21, 2016
    Sikhi Questioning Faith Sikh Sikhi Sikhism Mar 3, 2016
    Entering into Sikhism: Questions on Reht Maryada. Blogs Oct 22, 2015

  3. Douglas J Steele

    Douglas J Steele
    Expand Collapse
    Guest

    I'm not sure one is going to be significantly different than the other.

    If you're going to share, though, make sure you split the application into a
    front-end (containing the queries, forms, reports, macros and modules) and a
    back-end (containing just the tables).

    Only the back-end should be on the server: each user should have his/her own
    copy of the front-end, preferably on their hard drive.

    --
    Doug Steele, Microsoft Access MVP
    http://I.Am/DougSteele
    (no e-mails, please!)


    "Eric @ CMN, Evansville" <EricCMNEvansville@discussions.microsoft.com> wrote
    in message news:30E41394-05FB-4E6F-A797-9599DB2E5F76@microsoft.com...
    > Is it more efficient to have a rather complex, single query based on

    several
    > tables, or have a fairly simply query that is based on several other

    simple
    > queries that are ultimately based on single tables each ?
    >
    > I'm inheriting a database application that just seems to me to be of a
    > rather inefficient design. Any thoughts on efficiency and speed would be
    > appreciated.....by the way, this will become a shared database being run

    on a
    > network.
    >
    > Thanks !
     
  4. Eric @ CMN, Evansville

    Eric @ CMN, Evansville
    Expand Collapse
    Guest

    Thanks for the comments....I was planning on splitting the application.....on
    that note I have another question: what are the ramifications if a
    particular user does not have Access installed on his local machine ? I know
    I can create an MDE file for him, but just exaclty what does that mean in
    relation to the split database and the back-end being on a server ? Can I
    still do all that, and will it work, without much degredation in performance ?

    Thanks !

    "Douglas J Steele" wrote:

    > I'm not sure one is going to be significantly different than the other.
    >
    > If you're going to share, though, make sure you split the application into a
    > front-end (containing the queries, forms, reports, macros and modules) and a
    > back-end (containing just the tables).
    >
    > Only the back-end should be on the server: each user should have his/her own
    > copy of the front-end, preferably on their hard drive.
    >
    > --
    > Doug Steele, Microsoft Access MVP
    > http://I.Am/DougSteele
    > (no e-mails, please!)
    >
    >
    > "Eric @ CMN, Evansville" <EricCMNEvansville@discussions.microsoft.com> wrote
    > in message news:30E41394-05FB-4E6F-A797-9599DB2E5F76@microsoft.com...
    > > Is it more efficient to have a rather complex, single query based on

    > several
    > > tables, or have a fairly simply query that is based on several other

    > simple
    > > queries that are ultimately based on single tables each ?
    > >
    > > I'm inheriting a database application that just seems to me to be of a
    > > rather inefficient design. Any thoughts on efficiency and speed would be
    > > appreciated.....by the way, this will become a shared database being run

    > on a
    > > network.
    > >
    > > Thanks !

    >
    >
    >
     
  5. Douglas J. Steele

    Douglas J. Steele
    Expand Collapse
    Guest

    All users must have Access installed on their machine or they will be unable
    to use the application.

    This includes MDEs: they're not stand-alone executables.

    --
    Doug Steele, Microsoft Access MVP
    http://I.Am/DougSteele
    (no e-mails, please!)



    "Eric @ CMN, Evansville" <EricCMNEvansville@discussions.microsoft.com> wrote
    in message news:6CCD56BF-E5AB-42CC-B788-7601C43194B6@microsoft.com...
    > Thanks for the comments....I was planning on splitting the
    > application.....on
    > that note I have another question: what are the ramifications if a
    > particular user does not have Access installed on his local machine ? I
    > know
    > I can create an MDE file for him, but just exaclty what does that mean in
    > relation to the split database and the back-end being on a server ? Can I
    > still do all that, and will it work, without much degredation in
    > performance ?
    >
    > Thanks !
    >
    > "Douglas J Steele" wrote:
    >
    >> I'm not sure one is going to be significantly different than the other.
    >>
    >> If you're going to share, though, make sure you split the application
    >> into a
    >> front-end (containing the queries, forms, reports, macros and modules)
    >> and a
    >> back-end (containing just the tables).
    >>
    >> Only the back-end should be on the server: each user should have his/her
    >> own
    >> copy of the front-end, preferably on their hard drive.
    >>
    >> --
    >> Doug Steele, Microsoft Access MVP
    >> http://I.Am/DougSteele
    >> (no e-mails, please!)
    >>
    >>
    >> "Eric @ CMN, Evansville" <EricCMNEvansville@discussions.microsoft.com>
    >> wrote
    >> in message news:30E41394-05FB-4E6F-A797-9599DB2E5F76@microsoft.com...
    >> > Is it more efficient to have a rather complex, single query based on

    >> several
    >> > tables, or have a fairly simply query that is based on several other

    >> simple
    >> > queries that are ultimately based on single tables each ?
    >> >
    >> > I'm inheriting a database application that just seems to me to be of a
    >> > rather inefficient design. Any thoughts on efficiency and speed would
    >> > be
    >> > appreciated.....by the way, this will become a shared database being
    >> > run

    >> on a
    >> > network.
    >> >
    >> > Thanks !

    >>
    >>
    >>
     
  6. Eric @ CMN, Evansville

    Eric @ CMN, Evansville
    Expand Collapse
    Guest

    Thanks for the reply...and for clearing up my apparent misunderstanding on
    MDEs.

    "Douglas J. Steele" wrote:

    > All users must have Access installed on their machine or they will be unable
    > to use the application.
    >
    > This includes MDEs: they're not stand-alone executables.
    >
    > --
    > Doug Steele, Microsoft Access MVP
    > http://I.Am/DougSteele
    > (no e-mails, please!)
    >
    >
    >
    > "Eric @ CMN, Evansville" <EricCMNEvansville@discussions.microsoft.com> wrote
    > in message news:6CCD56BF-E5AB-42CC-B788-7601C43194B6@microsoft.com...
    > > Thanks for the comments....I was planning on splitting the
    > > application.....on
    > > that note I have another question: what are the ramifications if a
    > > particular user does not have Access installed on his local machine ? I
    > > know
    > > I can create an MDE file for him, but just exaclty what does that mean in
    > > relation to the split database and the back-end being on a server ? Can I
    > > still do all that, and will it work, without much degredation in
    > > performance ?
    > >
    > > Thanks !
    > >
    > > "Douglas J Steele" wrote:
    > >
    > >> I'm not sure one is going to be significantly different than the other.
    > >>
    > >> If you're going to share, though, make sure you split the application
    > >> into a
    > >> front-end (containing the queries, forms, reports, macros and modules)
    > >> and a
    > >> back-end (containing just the tables).
    > >>
    > >> Only the back-end should be on the server: each user should have his/her
    > >> own
    > >> copy of the front-end, preferably on their hard drive.
    > >>
    > >> --
    > >> Doug Steele, Microsoft Access MVP
    > >> http://I.Am/DougSteele
    > >> (no e-mails, please!)
    > >>
    > >>
    > >> "Eric @ CMN, Evansville" <EricCMNEvansville@discussions.microsoft.com>
    > >> wrote
    > >> in message news:30E41394-05FB-4E6F-A797-9599DB2E5F76@microsoft.com...
    > >> > Is it more efficient to have a rather complex, single query based on
    > >> several
    > >> > tables, or have a fairly simply query that is based on several other
    > >> simple
    > >> > queries that are ultimately based on single tables each ?
    > >> >
    > >> > I'm inheriting a database application that just seems to me to be of a
    > >> > rather inefficient design. Any thoughts on efficiency and speed would
    > >> > be
    > >> > appreciated.....by the way, this will become a shared database being
    > >> > run
    > >> on a
    > >> > network.
    > >> >
    > >> > Thanks !
    > >>
    > >>
    > >>

    >
    >
    >
     

Share This Page