Cursor pauses in Access 2007

[DIH]

When clicking in a new record in a continuous form, the cursor will
blink 3 or 4 times and then stop (sometimes for as long as 15 seconds).
If you start to type right away and keep typing (without stopping) there
are no pauses. When you click into a different field (even on the same
record)again, you get the pause. This form has no sub forms. There are 4
combo boxes, 10 text boxes for integers and 1 text box for memo data.

The file is located on a Novell Netware server. A copy of the database
runs without this problem when it's on the pc's local hard drives. It
only occurs on Access 2007. Other pc's running Access 2000, 2002 and
2003 show no signs whatsoever of this issue.

The server was rebooted but that had no effect. The pc's (3 of
them)where this is occurring are brand new and are running Windows XP.
Hardware: P4 3+ GHz, 1 Gb ram.

I've also noticed this problem on small, simple databases as well
(although the pause time is only a few seconds - still noticeable though).

I got to believe it's a network issue, but before I get the IT guys
really involved (even though I know it's there job - they're dealing
with a new roll out of hardware and software) I thought I would send
some feelers out in the newsgroup.

Any suggestions are greatly appreciated.

Dave

 

[NetworkTrade]

I think you semi solved the problem when you note that "A copy of the database

runs without this problem when it's on the pc's local hard drives".

I would tend to think it is this PC's relative location on the lan rather
than the version of Access (more segments between pc & server). Possibly the
PC's ability to communicate on the lan (slow network adapter).

Of course you can check this by swapping pc's - put a fast pc in location of
the slow and vice versa.... It would seem to me that if you swap and the
slowness is the same physical location - but now a different pc that tell you
one thing that it is the network location.

If the slowness stays with the Access07 machine in a new location and
another machine in its old position is fast; then it could be the NIC but it
could be the Access07 I suppose. Doesn't yet solve the problem totally but
helps isolate...

 

[DIH]

I think you semi solved the problem when you note that "A copy of the database

I would tend to think it is this PC's relative location on the lan rather
than the version of Access (more segments between pc & server). Possibly the
PC's ability to communicate on the lan (slow network adapter).

Of course you can check this by swapping pc's - put a fast pc in location of
the slow and vice versa.... It would seem to me that if you swap and the
slowness is the same physical location - but now a different pc that tell you
one thing that it is the network location.

If the slowness stays with the Access07 machine in a new location and
another machine in its old position is fast; then it could be the NIC but it
could be the Access07 I suppose. Doesn't yet solve the problem totally but
helps isolate...

Thanks for your response. My bad that I failed to mention that the 3
pc's were replacements for much older ones that were running Access 2000
and therefore their placement on the lan did not change.

I also noticed today that the same problem happens when moving from one
field to another directly in the tables data sheet view.

 

[NetworkTrade]

still sounds like the communication to the back end is flaky....

could be nic
could be memory in that pc is a bit too small
could be port into hub has gone soft
even a flaky network cord can cause alot of resends and slow down the coms
an insanely busy application in the background like scanning for viruses or
something....

hardware change out is when things on the edge finally break...so...

am not an Access07 apologist...could be Access07 too

hows the browsing with the machine around the network or internet? would be
using the same coms...check to see if that is slow too....

to isolate at some point you have to change things logically and see....
you could load Access07 on one of the fast machines and see if it stays
fast...if so then it is something else...

 

[DIH]

still sounds like the communication to the back end is flaky....

could be nic
could be memory in that pc is a bit too small
could be port into hub has gone soft
even a flaky network cord can cause alot of resends and slow down the coms
an insanely busy application in the background like scanning for viruses or
something....

hardware change out is when things on the edge finally break...so...

am not an Access07 apologist...could be Access07 too

hows the browsing with the machine around the network or internet? would be
using the same coms...check to see if that is slow too....

to isolate at some point you have to change things logically and see....
you could load Access07 on one of the fast machines and see if it stays
fast...if so then it is something else...

O.K. Here seems to be the bomb for Access 2007. The IT dept and I tested
this on a very high end machine (located right next to the server). This
pc has both Access 2003 and 2007 installed. Everything runs nice and
smooth on 03 and lags and pauses on 07. He believes it to be an XML
issue. Browsing the internet and around the network also is fine.

NetworkTrade - Thank you for all your input. It is much appreciated!

 

[NetworkTrade]

--
NTC

O.K. Here seems to be the bomb for Access 2007. The IT dept and I tested
this on a very high end machine (located right next to the server). This
pc has both Access 2003 and 2007 installed. Everything runs nice and
smooth on 03 and lags and pauses on 07. He believes it to be an XML
issue. Browsing the internet and around the network also is fine.

NetworkTrade - Thank you for all your input. It is much appreciated!

 

[NetworkTrade]

looks like you've done the ultimate comparison... and it doesn't look good
for Access07. Not sure the MVPers are plugged into this dialog.

clearly Access07 can not survive this bug because split dbs are the norm -
so it will need to be addressed.

I will hesitate implementing any split 07s until I see more about this....