Question about Access across a network "Rick A" <allisonrja[ at ]hotmail.com> 06.09.2006 16:17:34 I'm experiencing extremely poor response on my front-end application when it connects to a back-end database across a network. I've set up a real simple network. Three Windows XP computers and one hub. Each computer is given it's own IP address: 192.168.0.1, 192.168.0.2, and 192.168.0.3. One computer is the main computer and the other two are satellites. I shared out the folder were the back-end database is located. The back-end database is an Access 2000 format mdb. All computers are running Access 2003. The application is an Access 2000 based mde. When I access the back-end database directly via windows explorer the response is quick and acceptable. When I open the program and try to relink it takes an unacceptably long time. For example: relinking on the main computer takes 5 seconds. Relinking on the satellite computer takes 5 minutes maybe longer. Where can I go to find tips or tricks for connecting a front-end application to a back-end database across a network? Or does anyone know why I'm having such poor response time? Thanks, -- Rick

Re: Question about Access across a network "Albert D. Kallal" <PleaseNOOOsPAMmkallal[ at ]msn.com> 07.09.2006 11:33:53 [Quoted Text] >Relinking on the satellite computer takes 5 minutes maybe longer. I assume the above ONLY occurs when other users have the back end mdb file open. Most of the time, this is not much of a problem, and you simply distribute that mde to EACH computer. So, you pre-link the file BEFORE you distribute. And, really, linking is a one time deal, and not done every day. However, if you do have your own re-link code, after the first table is linked, open it to a temp/dummy reocrdset. The rest of the linking will now occur a full speed (this trick is know as a persistent connection, and will ALSO FIX your slow response time). > Where can I go to find tips or tricks for connecting a front-end > application to a back-end database across a network? Or does anyone know > why I'm having such poor response time? The persistence trick is outlined in the following link, and it also outlines the other things to check. Make sure you work though the whole list. the results should give you back your performance. http://www.granite.ab.ca/access/performancefaq.htm -- Albert D. Kallal (Access MVP) Edmonton, Alberta Canada pleaseNOOSpamKallal[ at ]msn.com

Re: Question about Access across a network "Rick A" <allisonrja[ at ]hotmail.com> 08.09.2006 12:38:02 Albert, Thanks for the link. I will give it a try and see what happens. As you suggested, the issue occurs when others have the back end mdb open. -- Rick Allison "Albert D. Kallal" <PleaseNOOOsPAMmkallal[ at ]msn.com> wrote in message news:%23TfGBGn0GHA.3464[ at ]TK2MSFTNGP03.phx.gbl... [Quoted Text] > >Relinking on the satellite computer takes 5 > minutes maybe longer. > > I assume the above ONLY occurs when other users have the back end mdb file > open. Most of the time, this is not much of a problem, and you simply > distribute that mde to EACH computer. So, you pre-link the file BEFORE > you distribute. And, really, linking is a one time deal, and not done > every day. > > However, if you do have your own re-link code, after the first table is > linked, open it to a temp/dummy reocrdset. The rest of the linking will > now occur a full speed (this trick is know as a persistent connection, and > will ALSO FIX your slow response time). > >> Where can I go to find tips or tricks for connecting a front-end >> application to a back-end database across a network? Or does anyone know >> why I'm having such poor response time? > > The persistence trick is outlined in the following link, and it also > outlines the other things to check. Make sure you work though the whole > list. the results should give you back your performance. > > http://www.granite.ab.ca/access/performancefaq.htm > > -- > Albert D. Kallal (Access MVP) > Edmonton, Alberta Canada > pleaseNOOSpamKallal[ at ]msn.com >

Re: Question about Access across a network "Alp Bekisoglu" <alp[ at ]access_ng.com> 10.09.2006 08:14:37 Hi Albert & Rick, Sorry for jumping in like this but the situation is similar in my case as well with a slight + that is I have 5 backends (each consists of different type of data i.e. accounts, general company data, clients data, etc). Would it mean to do the same (persistent connection) for each one? Thanks, Alp "Albert D. Kallal" <PleaseNOOOsPAMmkallal[ at ]msn.com> wrote in message news:%23TfGBGn0GHA.3464[ at ]TK2MSFTNGP03.phx.gbl... [Quoted Text] > >Relinking on the satellite computer takes 5 > minutes maybe longer. > > I assume the above ONLY occurs when other users have the back end mdb file > open. Most of the time, this is not much of a problem, and you simply > distribute that mde to EACH computer. So, you pre-link the file BEFORE > you distribute. And, really, linking is a one time deal, and not done > every day. > > However, if you do have your own re-link code, after the first table is > linked, open it to a temp/dummy reocrdset. The rest of the linking will > now occur a full speed (this trick is know as a persistent connection, and > will ALSO FIX your slow response time). > >> Where can I go to find tips or tricks for connecting a front-end >> application to a back-end database across a network? Or does anyone know >> why I'm having such poor response time? > > The persistence trick is outlined in the following link, and it also > outlines the other things to check. Make sure you work though the whole > list. the results should give you back your performance. > > http://www.granite.ab.ca/access/performancefaq.htm > > -- > Albert D. Kallal (Access MVP) > Edmonton, Alberta Canada > pleaseNOOSpamKallal[ at ]msn.com >

Re: Question about Access across a network t568aort568b[ at ]aol.com 20.09.2006 21:14:40 Open a very small table during the autoexec and leave it open hidden. This will speed things up.