DatabaSe runnign very slow

  • Thread starter Thread starter Bob
  • Start date Start date
B

Bob

I have a database application. It has a back-end on a Windows NT server.
The database is in Access 97 with a few of the tables linked to a SQL
database.

Most of the workstations are W98 (one is Millennium) running Access 97.
These work fine.

The problem workstation runs Windows XP Home and Access XP. It ran fine
until a few days ago. I can log on just fine. That requires the front-end
to connect through the back-end to the SQL database.

But when I open a form that is bound to one of the A97 tables, it takes a
long time (approx 45 seconds) for a simple form where you select the job to
work on. This form is up in less than 2 seconds on all of the other
workstations.

Every other network function seems to be running fine.

Does anyone have any ideas as to what might be going on here? I’ve checked
references and everything appears fine. I’ve copied an original copy of the
front-end and tried running it as a A97, A2000, and A2002 file. All of them
run the same. Compiling doesn’t reveal any errors. I’ve compacted and
repaired the back-end. HELP!!
 
We are assuming that each workstation gets its own copy of the front end
(right, that is standard setup, and I shall assume you are doing this, and
NOT running the front end from the server).

It turns out that windows XP has a complete different file system then does
win98 (all kinds of security stuff that win98 does not have). Thus, to
restore performance, the solution is to ALWAYS keep a table opened from the
front end to the back end. (this only applies to the file share...and not
sql server).

So, try opening a table to the back end, it will restore your performance to
win98 levels.

While the following applies to win2000, many of the tricks mentioned ALSO
apply to a97. Check the following list of things to check:

http://www.granite.ab.ca/access/performancefaq.htm
 
I tried the things in the link you provided. Still running slow from that
one workstation.

Anyone have any ideas what might be going on.


Albert D. Kallal said:
We are assuming that each workstation gets its own copy of the front end
(right, that is standard setup, and I shall assume you are doing this, and
NOT running the front end from the server).

It turns out that windows XP has a complete different file system then does
win98 (all kinds of security stuff that win98 does not have). Thus, to
restore performance, the solution is to ALWAYS keep a table opened from the
front end to the back end. (this only applies to the file share...and not
sql server).

So, try opening a table to the back end, it will restore your performance to
win98 levels.

While the following applies to win2000, many of the tricks mentioned ALSO
apply to a97. Check the following list of things to check:

http://www.granite.ab.ca/access/performancefaq.htm


--
Albert D. Kallal (MVP)
Edmonton, Alberta Canada
(e-mail address removed)
http://www.attcanada.net/~kallal.msn\
Click to expand...

I have a database application. It has a back-end on a Windows NT server.
The database is in Access 97 with a few of the tables linked to a SQL
database.

Most of the workstations are W98 (one is Millennium) running Access 97.
These work fine.

The problem workstation runs Windows XP Home and Access XP. It ran fine
until a few days ago. I can log on just fine. That requires the front-end
to connect through the back-end to the SQL database.

But when I open a form that is bound to one of the A97 tables, it takes a
long time (approx 45 seconds) for a simple form where you select the job to
work on. This form is up in less than 2 seconds on all of the other
workstations.

Every other network function seems to be running fine.

Does anyone have any ideas as to what might be going on here? I've checked
references and everything appears fine. I've copied an original copy of the
front-end and tried running it as a A97, A2000, and A2002 file. All of them
run the same. Compiling doesn't reveal any errors. I've compacted and
repaired the back-end. HELP!!
 
Back
Top