Re: Linked Tables

Tech Tip: Click here to run a free scan for Windows Errors and optimize PC performance


Thanks Allen and Klatuu.

I mentioned the file being on a server to demonstrate that running it as a
single file on a server runs far faster than as split files on a server -
i.e. that network speeds were not, of themselves, a noticeable contributing
factor. Front-ends will, of course, be on local machines once the database is
in production. I am also currently trying to run the front-end on my local
PC, but with these disastrously slow results.

Allen, I will refer to the link you have given and get back if necessary.
Thanks.

"Klatuu" wrote:

Could be. And that would only make it worse.
--
Dave Hargis, Microsoft Access MVP


"Allen Browne" wrote:

Good pickup, Dave.

That possibly means multiple users are in the same front end also.

--
Allen Browne - Microsoft MVP. Perth, Western Australia
Tips for Access users - http://allenbrowne.com/tips.html
Reply to group, rather than allenbrowne at mvps dot org.

"Klatuu" <Klatuu@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote in message
news:54A53B51-57E1-4FB8-9C80-6EF2EB5B076B@xxxxxxxxxxxxxxxx
Note the OP said both the front and back ends are on a network folder.
This
is going to dramatically increase network traffic and thus slow the
application.

It would be much better if the front end is on the user's computer.
--
Dave Hargis, Microsoft Access MVP


"Allen Browne" wrote:

Follow through the list of things Tony has here:
http://www.granite.ab.ca/access/performancefaq.htm

The split database will be a little slower, but should not orders of
magnitude slower.

"Rod" <Rod@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote in message
news:36CAB092-74C9-4FCE-9E29-23159188BD2A@xxxxxxxxxxxxxxxx
A single .mdb file, containing tables, queries, forms and code, runs at
an
acceptable speed whether from a local drive or from a network drive.

Split the file, moving the tables to a back-end and then linking them
to
the
front-end, and it runs incredibly slowly. A query which ran in under a
second
now takes over a minute!

Running the single file off a network drive works fine. Split the file,
placing front-end and data in the same network directory, and it grinds
to
a
halt.

I am very familiar with Access and have done this many times before
with
success. Can anybody suggest some pointers as to what is causing this
dramatic slowdown?


.

Relevant Pages

  • Re: Split DB over network
    ... > I have a DB sitting on a server. ... > sits on server, ... > The network it is running on is a little unreliable - does ... Bruce M. Thompson, Microsoft Access MVP ...
    (microsoft.public.access.setupconfig)
  • Re: Security Question
    ... to determine their network ID. ... Doug Steele, Microsoft Access MVP ... Database is on the server. ... Each teacher computer on the network has a ...
    (microsoft.public.access.gettingstarted)
  • Re: Fully parallel Scheme-based language w/ evaluator
    ... Windows Server 2003 and networks in simple - and irreverent - terms. ... If networking really is a big deal, ... Concepts and Terminology in Part I, and The Design and Deployment of Network ...
    (comp.lang.misc)
  • Re: Outgoing POP3 email missing/lost/not received
    ... Funny thing is that I have had this ISP for 8 years and it has always been ... It looks like when you last ran CEICW, you set the ISP's mail server to: ... Internet Connection Wizard. ... After the wizard completes, the following network connection ...
    (microsoft.public.windows.server.sbs)
  • Re: Logon Server Unavailable
    ... There are currently no logon servers available to service ... You use a office laptop to connect the office VPN, when you map a network ... you may receive this message: "This account is the ... The server is not configured for transactions"> "A domain controller for your domain could not be contacted" ...
    (microsoft.public.windows.server.general)