Form record navigation slows down in Access 2003

[vicissitude]

Is there any common reasons why record navigation would suddenly slow down to an unusable speed if any records are input or removed?

The database is on a network and is fine if nothing is input or removed and will accept a few record changes but then after a while it will just grind to a halt forcing the database to be closed and opened again.

Thanks in advance.

 

[DCrake]

Have you run a compact an repair lately?

Is the database split?

Run C & R on both if split

 

[vicissitude]

It is not split and have run c&r and also decompile and recompile but to no avial.

Is there any commands to flush and refresh to save having to close and reopen database?

 

[DCrake]

Are more than one users using this app at the same time?

 

[vicissitude]

No multiple users, It is a newly written database, currently being tested.

 

[DCrake]

I feel you still need to split it, even if for developments purposes. Also to create an actual working configuration. This will bench test your application better and give a more acurate performance feedback.

Alot may depend on the overall size of the app as well.

 

[vicissitude]

I have split the database and tried it over the network but unfortunately it is excruciatingly slow this way. Unusably slow.

 

[DCrake]

Can you post a copy of the app to look at?

 

[vicissitude]

Yes i will get the app posted, that would be a great help, thanks.

 

[vicissitude]

Soz for the delay, not as normalised as i would like but best compromise i could come up with...

 

[missinglinq]

I have split the database and tried it over the network,,,

You've split the database, but where do you have the front end? It needs to be on the PC you're working from, not on the server.

In forced retirement, I've been working 10-12 hours a day, for the past five years, on half a dozen Access news groups/forums, and see this kind of thing regularly. It always comes down to a network problem, rather than a primary Access problem.

Linq ;0)>

 

[vicissitude]

I have to get this thing to work in a satelite office where it is working down a vpn, the office has a 10meg broadband connection for 6 computers. That is good news (or maybe not) that it is the network that is the cause. I have had to completly redesign parts of it just to get it to work to any degree of useability. If i dare to touch the form filter then it takes 2 mins just to close!

When i split the database i put the backend on the server and the front end in the satelite office and it was just too slow.

 

[gemma-the-husky]

i suspect you dont have a permanent connection. open a hidden form or a recordset bound to a dummy table.

If you don't have that access has to re-open the connections each time.

I think this is maybe to do with sharing violation notifications, discussed in MS KB article 889588. (interesting article about performance)

http://support.microsoft.com/kb/889588

 

[vicissitude]

Thanks for the link! very interesting,

Why is binding a recordset to a dummy table to keep the connection open different to having the one main form open all the time?

Because my problem happens when the main form is constanly being used. Is it because it is not bound directly to the table?