Acc 97: slow linked tables

[TC]

Make sure that the back-end db opens a connection to the front-end db with
the OpenDatabase statement (for example). The connection should be hekld
open for the duration of the run. This stops Access having to continually
create, then delete, an LDB file on the server, as each form is opened, and
closed, respectively. Searching these groups for relevant terms will
doubtless tell you more. (opendatabase, "persistent connection", "slow
response", etc.)

HTH,
TC

 

[Chris Vandewiele]

Hi,

1) Network configuration
I have a program in access 97. The .mde file is on the
client (windows NT4 workstation SP6A) and the
datafiles .mdb are on the server (windows 2000 server
SP3). I work with linked tables in the .mde program file.
The network lines are 100 Mhz.

When i put everyting on the client (.mde, .mdb) everything
is very fast. When i use the network configuration. The
forms on the linked tables are going very slow.
How can i make things faster working with the network
configuration? I tried it with converting to Access 2000
or XP it is still the same problem. SLOW, SLOW ....

Thank you
Chris Vandewiele

 

[Tim Ferguson]

When i put everyting on the client (.mde, .mdb) everything
is very fast. When i use the network configuration. The
forms on the linked tables are going very slow.

In addition to what TC says, there are some network issues to check -- for
example one failing NIC _anywhere_ on the network (i.e. not neccessarily on
the path between client and server) can slow down access and also risk
damaging the data file too.

In terms of bandwidth, you should be _extremely_ parsimonious about the
amount of data you request. Banish all "SELECT *" commands, and never,
ever, open tables for forms. Always use WHERE clauses to limit the number
of records requested, preferably to just the one that the user is editing.

Finally, if things are still slow, consider using SQL server or MSDE. The
point is that jet will send entire pages of mdb file up the network, even
if you only ask for one value. Things like DSum() will get the entire table
whether you want it or not. With a database server, the summing gets done
by the server, and only one number value is sent across the network -- much
better.

Hope that helps


Tim F