From: johnk@pceffect.co.uk   
      
   Opening the Access database on the local LAN is fine. And the local   
   LAN is WLAN 802.11b so not the fastest in the world!   
      
   Worse, the database I've been testing with is about 1/10th the size of   
   the operational database we want to get to!   
      
   I'm thinking of re-structuring the database, but meanwhile will test   
   with some ordinary files like Word documents   
      
   Thanks   
      
   JohnK   
      
      
   On Tue, 24 Feb 2004 19:51:55 +0100, Martin Bodenstedt   
    wrote:   
      
   >John F Kappler wrote:   
   >   
   >> I've finally managed to get VPN working for our remote notebook users.   
   >>   
   >> They are now dialing-in to an ISP, making their VPN connection and   
   >> then trying to open an Access database on our file server. Great.   
   >> However......   
   >>   
   >> Performance is very slow, so my question is, what is likely to be the   
   >> worst bottleneck? Is it the dial-up connection, coming in at 30k? Or   
   >> the broadband link to the office which is a standard 500? Or is it the   
   >> way that Access handles the database files?   
   >   
   >Hmmm,   
   >   
   >if one end uses a 30k dialin connection and the other end a "standard   
   >500" then that end certainly is not the bottleneck.   
   >   
   >What you have to bear in mind is that VPN adds a little overhead to your   
   >IP traffic (the tunnel envelope) so You might want to reduce MTU size a   
   >little on the client side (to reduce packet fragmentation).   
   >   
   >What happens if you open the access database (using the same   
   >application) when on the local LAN?   
   >   
   >   
   >--   
   >Martin Bodenstedt   
   >   
   >www.maboko.de / www.die-bodenstedts.de   
      
   --- SoupGate-Win32 v1.05   
    * Origin: you cannot sedate... all the things you hate (1:229/2)