Access 2003 SP3 slow when online

[DIH]

I recently upgraded to Access 2003 (sp3) from Access XP. Now, when I
open a table or view a query in design view, there is quite a long
pause. It also takes quite a while to exit the db as well as look at the
table relationships. I see there is network activity during all these
actions. I made sure to turn off all online help options but still have
the same issue. The database is split into a frontend/backend. When I
turn my dsl router off, everything opens/closes and runs fast. I have
never experienced this issue with Access XP.

Any help is greatly appreciated.

Dave

 

[Arvin Meyer [MVP]]

Very possibly you AntiVirus program may be interfering with reads and
writes. Access 2003 does use more resources than 2002, but not noticeably
more. Have a look at Tony Toew's performance FAQ and see if anything helps:

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

 

[Tony Toews [MVP]]

I recently upgraded to Access 2003 (sp3) from Access XP. Now, when I
open a table or view a query in design view, there is quite a long
pause. It also takes quite a while to exit the db as well as look at the
table relationships. I see there is network activity during all these
actions. I made sure to turn off all online help options but still have
the same issue. The database is split into a frontend/backend. When I
turn my dsl router off, everything opens/closes and runs fast. I have
never experienced this issue with Access XP.

Now that's a very interesting problem. Especially with the DSL router
turned off.

Are all your linked tables to the same BE MDB? Is one of them on a
different network server?

You can use the following code to view the Connect strings

Sub ConnectString()

Dim db As DAO.Database, tdf As TableDef

Set db = CurrentDb

For Each tdf In db.TableDefs
If Len(tdf.Connect) > 0 Then _
Debug.Print tdf.Connect & " " & tdf.Name
Next

End Sub

Tony
--
Tony Toews, Microsoft Access MVP
Please respond only in the newsgroups so that others can
read the entire thread of messages.
Microsoft Access Links, Hints, Tips & Accounting Systems at
http://www.granite.ab.ca/accsmstr.htm
Tony's Microsoft Access Blog - http://msmvps.com/blogs/access/

 

[DIH]

Now that's a very interesting problem. Especially with the DSL router
turned off.

Are all your linked tables to the same BE MDB? Is one of them on a
different network server?

You can use the following code to view the Connect strings

Sub ConnectString()

Dim db As DAO.Database, tdf As TableDef

Set db = CurrentDb

For Each tdf In db.TableDefs
If Len(tdf.Connect) > 0 Then _
Debug.Print tdf.Connect & " " & tdf.Name
Next

End Sub

Tony

Thanks guys. I discovered a couple of things. There was a back end table
that was still linked to a network share (from my work network). I fixed
that but still had the slow issues. I then tried stopping my Avast anti
virus protection and wham, everything started to fly. The strange thing
now is after re-starting the AV protection, it still flies!
Now I'm stumped (but still happy that there is no longer the speed
issue). I'll run through these things again with another copy of the db
(one that still has the incorrect network linkage) and see what happens.

Once again, many thanks!

Dave


Dave

 

[david]

Faster with the DSL turned off may indicate a "Network Browsing"
issue.

Windows likes to try to keep track of where things are, to
optimise access. It Browses the network to find the things
you have used, are trying to use, or might use again. If it
can't find things, it only knows because it has asked, and
there is no response before timeout.

This wait for timeout process can make a lot of things
slow. It can make your broken links slow. It can make
your AV slow. Conversely, your broken links or AV
update or AV scan can trigger network browsing with
timeout that makes other things slow.

A solution to Network Browsing timeouts is to find
and remove all broken links in Windows and all programs
- not just Access.

(david)

 

[Paul Shapiro]

If you antivirus has the option, it's good to exclude the db from scanning.
Depending on your preferences, you could exclude the folder(s) containing
the back-end and front-end db, or exclude all .mdb, .mde, etc. files.

 

[DIH]

Yep, I agree with everything you said. It was a table that was
incorrectly linked to a network share. All is well now.

Thanks to everyone for their help.

Dave