Ms Access hang when accessed through network

[epla]

hi there

here is the case,,

We have Ms Access database on w2k server (size 1.3 GB), actually it is
mainly used for registering student on our university. we are using this
database since 3 years and no problems.
suddenly , yesterday , while users accessing the database (read+write) from
there machines (xp and windows 2000 proffessional), it looks slow and slow ,
and finally it hangs (we r using Ms office xp).
this case repeated many times yesterday, I dont know what had happened, i
ask the programmer , he said i didnt change anything, i try to move the
database to a new server, it works fine for 1 hours , and the problem
comeback again,, the programmer move the database to his local machine
(windows 2000 proffessional)and share it, they are working fine without any
problems!!!!
i double check my servers and network, it is 100% fine!!!!!!!

any solution

thanx in advance

Best Regards

 

[Pete Sheridan]

Hello "epla",

A 1.3GB file size is large for an Access DB.

The first question is - Has anyone Compacted and Repaired
the database lately? If not, Copy the DB file to a
backup copy and then try to 'Compact and Repair' the
original file using the built in tool that comes
with 'Access'.

If you haven't run this tool it is easy to find.
Open the Microsoft Access appilcation but do not open the
database. Now at the top of the screen, just below the
blue header that says 'Microsoft Access', you will find
the menu bar. click on 'Tools' and ''Database Utilities'
will be displayed. Select the 'Compact and Repair'
utility and it will open the 'Database to Compact from'
window. Find your database file and select it.

After a small time, you will be presented with
the 'Compact Database Into' window. Select the same
database file that you selected before and add a change
to the file name to save the compacted file to. The way
I do it is as follows:
Original filename: DatabaseXYZ.mdb
Compacted Filename: DatabaseXYZ_New.mdb

Understand that if you have never compacted the db, it
will taks a bit of time to do it (especially with a 1.3GB
file). Let it run!

After the db compacts, you can rename the original file
from 'DatabaseXYZ.mdb' to 'DatabaseXYZ_oldYYMMDD.mdb' and
then rename the compacted filename
from 'DatabaseXYZ_New.mdb' to 'DatabaseXYZ.mdb'. Now run
the new compacted copy of the DB. If it runs, you're ok
and have dodged a bullet (this time). Also, make sure
to 'Compact' the DB as often as possible!!!

There are other ways to do this proceedure but this way
gives you a copy of the old file and a copy of the new
file.

Last but not least, Is the DB part of a split environment
or is it one big file that contains all of the tables,
forms, reports, queries, etc.

If it is one big file, try splitting it into a 'front-
end' and a 'back-end' environment. This will give you a
bit of breathing room.

One other suggestion is to split out the data into SQL
Server and keep the 'Fromt-End' (forms, queries, reports,
etc) in an Access DB with links to the SQL Server data
tables. This will provide a self tuning and compacting
environment for the data (the part that grows the most).

Hope this helps, Pete




-----Original Message-----

 

[Ken Snell [MVP]]

1.3 GB is too large? Not for ACCESS 2000 and up.