Fix Bug in MS Access 2003-scrolling on table records crashes all.

[Dan Patrick]

When I do a fast scroll on records in an opened table by positioning the
mouse cursor in the gray area of the scroll bar below the current position
indicator and clicking the left mouse button and holding it down the entire
access database crashes. This problem occurs on several different machines
with the same version of Access 2003 installed (SP2 11.6566.8036)

----------------
This post is a suggestion for Microsoft, and Microsoft responds to the
suggestions with the most votes. To vote for this suggestion, click the "I
Agree" button in the message pane. If you do not see the button, follow this
link to open the suggestion in the Microsoft Web-based Newsreader and then
click "I Agree" in the message pane.

http://www.microsoft.com/office/com...b41&dg=microsoft.public.access.tablesdbdesign

 

[Allen Browne]

Dan, I appreciate that you intended this for Microsoft, but a quick response
from a fellow Access developer.

I just tried what you described on a table with 900k records, holding the
button down and scrolling for more than a minute and did not experience a
crash. There must therefore be something else going on here.

Presumably you have tried a compact'n'repair, which should fix the problem
if the crash is caused by a bad index. If your database is split, be sure to
compact both the back end (since that holds the tables and indexes) and the
front end (since that holds cached info on the tables, and can cause
crashes.)

If the data is attached from another data source, there may be a problem
with the driver, or the other file.

If the table has memo or OLE Object fields, there may be a record with a bad
pointer. You may be able to identify that record and remove it (or copy all
other records to a new table if it cannot be removed.)

The operation you describe is also video-related. It is possible that it is
connected with a problem graphics driver, though this is less likely if the
different machines you described have different graphics cards/drivers. If
you are using Windows XP, you might want to temporarily revert to the
Windows Classic theme to see if that solves the problem, since there are
issues with the scrollbars under XP.

It would also be worth running ChkDsk to ensure the file is not crosslinked.

If the data file is across a network, you might copy it locally, to
eliminate the possiblity that the problem is related to flawed network or
latency issues.

You probably want to turn off Subdatasheets on this table to eliminate that
factor too.

The basic troubleshooting tactic is to eliminate anything that could
contribute to the problem--even other software such as screen saver,
antivirus, email client, ...

Hope something amongst that is of use to you.

 

[Dan Patrick]

Thanks for your prompt response to this issue. I think the problem only
occurs if the database happens to be designed using MS Access 2000 and then
when Access 2003 opens the older database this occurs. I've tested this out
and found it to be true. While I don't expect Microsoft to act on this
request since 2000 has apparently gone the way of the doe-doe bird but It is
a pain in the but to traverse records expeditiously in older non-converted
databases. I would easily convert the database however we still have other
uses who only have Access 2000 installed on there machines. Another issue
related to compatability from older versions of Access is the issue of not
being able to open an older database in 2003 by clicking the icon directly.
Instead you would have to open Access 2003 and then from there open the older
database. But I digress.

Again, thank you for your quick response. Try this issue with an older
database and see what you get.

Dan Patrick

 

[Allen Browne]

The 900k db I referred to is in A2000 format.
That's the default format for a new A2003 install anyway.

There is an issue with Access 2003 vs Access 2000 related to the difference
in binary format (compiled code.) It is quite common to experience crashes
when swapping versions. The solution is to decompile, compact, and recompile
in the current version. But I don't see how this issue could relate to the
one you describe: you are talking about scrolling a table (not a query or
form), so there are no function calls being executed there.)