front end and back end
in [Forms]
|
From: iccsi on 30 Jun 2008 08:10 I just learned that it is efficient that split mdb to front end and back end database. I just wonder that does it mean that front end and back end communicate with SQL string and result set to reduce network traffic? Does it mean that query should store on the backend, because it will be faster front end sends a short query name instead of SQL string? Are there any other benefits? Your information is great appreicted,
From: Douglas J. Steele on 30 Jun 2008 08:47 Tony Toews and Albert Kallal have lots of information about the benefits of splitting applications at http://www.granite.ab.ca/access/splitapp/index.htm and http://members.shaw.ca/albertkallal/Articles/split/index.htm respectively. There's no benefit to be gained by putting the queries in the back-end. It's the front-end that runs the queries, not the back-end. -- Doug Steele, Microsoft Access MVP http://I.Am/DougSteele (no e-mails, please!) "iccsi" <inungh(a)gmail.com> wrote in message news:e29301b9-5b90-4e39-bc1a-0897dd7ca8a4(a)r66g2000hsg.googlegroups.com... >I just learned that it is efficient that split mdb to front end and > back end database. > > I just wonder that does it mean that front end and back end > communicate with SQL string and result set to reduce network traffic? > > Does it mean that query should store on the backend, because it will > be faster front end sends a short query name instead of SQL string? > > Are there any other benefits? > > Your information is great appreicted,
From: iccsi on 30 Jun 2008 11:10 On Jun 30, 8:47 am, "Douglas J. Steele" <NOSPAM_djsteele(a)NOSPAM_canada.com> wrote: > Tony Toews and Albert Kallal have lots of information about the benefits of > splitting applications athttp://www.granite.ab.ca/access/splitapp/index.htm > andhttp://members.shaw.ca/albertkallal/Articles/split/index.htm > respectively. > > There's no benefit to be gained by putting the queries in the back-end. It's > the front-end that runs the queries, not the back-end. > > -- > Doug Steele, Microsoft Access MVPhttp://I.Am/DougSteele > (no e-mails, please!) > > "iccsi" <inu...(a)gmail.com> wrote in message > > news:e29301b9-5b90-4e39-bc1a-0897dd7ca8a4(a)r66g2000hsg.googlegroups.com... > > > > >I just learned that it is efficient that split mdb to front end and > > back end database. > > > I just wonder that does it mean that front end and back end > > communicate with SQL string and result set to reduce network traffic? > > > Does it mean that query should store on the backend, because it will > > be faster front end sends a short query name instead of SQL string? > > > Are there any other benefits? > > > Your information is great appreicted,- Hide quoted text - > > - Show quoted text - Thanks for the link and information, Does it help application performance? it seems that the above links do not mention the performance. Thanks again,
From: Klatuu on 30 Jun 2008 12:02 If you are asking about performance difference based on the query being in the fe or the be, the fe will be faster. To expand a bit on the environment, Database engines like SQL Server, Oracle, Sybase, etc are Client/Server database engines. That means the logic to handle data requests runs in an instance of the database engine on the server. Therefore, less data has to be moved accross the network. The Client (Front End) only sends the information the database engine needs to satisfy the data request. The manipulation of the data happens at the server level and if records need to be returned, only the requested records are returned. Jet (the database engine used by Access) is a File/Server database engine. That is, no logic runs on the server. The server is only used to store the Back End mdb file that contains the tables and relationships. All logic is running on the Client (the user's computer). So when you execute a query, the Front end reads the query, evaluates it, and passes the request to Jet. Jet the reads the data in the mdb file on the server and first returns the index values from the table(s) in the Back End and uses the values to determine which records to retrieve. This means the index values are first passed accross the network, then the actual data is passed across the network. If the query is stored in the Back End mdb, Access first has to retrieve the query accross the network to pass it to Jet. This is an extra network trip. So, the short of it is the only objects that should be in the Back End mdb are tables, indexes, and relationships. All forms, reports, macros, modules, and DAP's should be in the front end. -- Dave Hargis, Microsoft Access MVP "iccsi" wrote: > On Jun 30, 8:47 am, "Douglas J. Steele" > <NOSPAM_djsteele(a)NOSPAM_canada.com> wrote: > > Tony Toews and Albert Kallal have lots of information about the benefits of > > splitting applications athttp://www.granite.ab.ca/access/splitapp/index.htm > > andhttp://members.shaw.ca/albertkallal/Articles/split/index.htm > > respectively. > > > > There's no benefit to be gained by putting the queries in the back-end. It's > > the front-end that runs the queries, not the back-end. > > > > -- > > Doug Steele, Microsoft Access MVPhttp://I.Am/DougSteele > > (no e-mails, please!) > > > > "iccsi" <inu...(a)gmail.com> wrote in message > > > > news:e29301b9-5b90-4e39-bc1a-0897dd7ca8a4(a)r66g2000hsg.googlegroups.com... > > > > > > > > >I just learned that it is efficient that split mdb to front end and > > > back end database. > > > > > I just wonder that does it mean that front end and back end > > > communicate with SQL string and result set to reduce network traffic? > > > > > Does it mean that query should store on the backend, because it will > > > be faster front end sends a short query name instead of SQL string? > > > > > Are there any other benefits? > > > > > Your information is great appreicted,- Hide quoted text - > > > > - Show quoted text - > > Thanks for the link and information, > Does it help application performance? > > it seems that the above links do not mention the performance. > > Thanks again, > >
From: Douglas J. Steele on 30 Jun 2008 12:25 Does what help application performance? Splitting the database? No. In fact, it can cause poorer performance, but the other benefits outweigh that. Tony does talk about it at http://www.granite.ab.ca/access/splitapp/performance.htm -- Doug Steele, Microsoft Access MVP http://I.Am/DougSteele (no e-mails, please!) "iccsi" <inungh(a)gmail.com> wrote in message news:d5753d04-5c06-4170-bb18-40b532012744(a)m44g2000hsc.googlegroups.com... Thanks for the link and information, Does it help application performance? it seems that the above links do not mention the performance. Thanks again,
|
Pages: 1 Prev: Automating/ Verifying data entry in a form Next: syntax error missing operator |