Access running slow from server.

[Mike]

Hi all,
Wasn't sure where in here to post this as it don't come
under existing Access Categories so here goes:
I have a few Access 2000 databases that live on a WinNT4
server that have become almost unbearable to use when
designing changes etc. Just to update a form field can
take up to 3 mins before being able to do anything. I have
monitored the server that these databases reside on and it
is always under 10% utilized and memory is not a prob.
These databases are not bug Say 1.5MB with Approx 100
records and have been compacted etc. I have done File
transfer tests to and from the server and no problem there
either. I have virus checked the whole server (as the prob
only started approx 2 weeks ago) and no, nothing. I tested
by creating a new database in same directory with some
dummy records etc and it flys along.. I have also Opened
the databases from other machines to verify that it was
not happening as a result of something screwy on the local
PC and this made no difference still slow. When the
database is copied to local PC it goes along fast as
expected. Any suggestions would be greatly appreciated and
thanks in advance.

 

[test joby]

Test Test Test

 

[GVaught]

test somewhere else Joby..

Mike,
you may need to split the database. If the full database resides on the
server and the user opens the database from their machine you will receive
latency problems as new users and data is added to the database.
Splitting the database is the ideal way to share an Access database with
multiple users.

The back-end (tables only) reside on your NT server. The front-end resides
on each user's machine. The front-end contains linked tables from the
back-end, queries, forms, reports, macros, and module code.

See help on Database-Splitter. It is real easy to do.

Note: Make a backup copy before splitting the database and split the
database at the local level and not from the NT Server.

If you continue to have slowness, then have the network admin test the
connection between the machines. However, since you said other machines seem
to have the same problem, then the split should help in that regard.

Good Luck

 

[Mike]

Thanks for that. I forgot to mention that this happens on both split and
unsplit databases.
Regards Mike.

 

[Mike]

I am starting to think it may be the first part of the Blaster virus.
Although the server has not got the balster virus it may well have been
compromised at port 135 and RPC error although not the virus, causes
erronious problems. Interesting to see.. After I back up the whole server
next week I will see after Service packing and patching and get back here
just for reference.
Mike.

 

[Albert D. Kallal]

The usual solution is to force the connection to stay open.

Try opening a table at application start-up. Leave this table open. Your
performance should return to normal.

There is a good list of other things to check, but the above is usually the
fix.

check out:

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