PLS HELP - Access DB Has slowed right down

[Matt]

Can anyone help?



We have been using a database for several years (MS Access 2003). The tables
are set up in a database on our server, and we have several other computers
accessing the information via MS Access fronts, with the main DB's tables
linked to each of the fronts.



This has been working fine for several years, but suddenly accessing the
data from every computer has slowed right down. Each of the fronts has there
own forms, queries and reports (only the tables are linked) but it is taking
up to 30seconds to open forms or carry out any other task.



We have tried doing a repair on the main DB and the fronts, and have also
pruned down much of the data, but this hasn't worked at all. In actual fact
each time we do anything to speed it up it seems to slow it down further.
There has been no events that we know of that could have triggered this and
all our other programs are working fine.



This database is our main invoicing and job tracking system so we need to
fix it urgently.



Can anyone please help with this as it is slowing our production down
considerably?



Thanks in advance



Matt

 

[John W. Vinson]

This has been working fine for several years, but suddenly accessing the
data from every computer has slowed right down. Each of the fronts has there
own forms, queries and reports (only the tables are linked) but it is taking
up to 30seconds to open forms or carry out any other task.

Have you installed or changed any antivirus software lately? Several AV
programs can interact badly with Access, especially if they're allowed to
monitor .mdb files.

 

[AlexM]

It might have more to do with your network setup than with Access.
Have someone confirm that you network infrastructure is ok.
Open each table and make sure there are no corrupt records.

 

[a a r o n _ k e m p f]

Access (Jet) runs like crap.

Upsize to SQL Server (ADP) if you give a shit about performance,
scalability or stability

 

[Matt]

I tried most of the suggestions this morning but to no avail, it was still
very slow.

I have fixed it however by creating a new DB and importing all tables into
it as per Phil's suggestion in another group (thanks) There is nothing
different about the
new DB to the old one apart from the name but it seems to be working fine
again.

Thanks again

Matt

 

[a a r o n _ k e m p f]

it's called _BLOAT_.

Jet has it-- the only way to get away from it is to upsize to SQL
Server