Revision History
Site Map

Graph: dbPix image storage vs OLE Embedding and Linking in Microsoft Access

The Access Image FAQ < Previous ArticleNext Article >

Preventing the "Scroll-too-Quick" Crash

Sample Newsgroup Questions 
Access 2000 General protection fault
Access crashes when scrolling too fast
Access crashes when moving through records with linked jpg images
System crashes when I move to fast from one record to the next
Rapid browsing crashes Access
Access crashes when user scrolls through a bound datasheet ...
Slowing Record Navigation
Load image crashes
Program Crash with Images in Forms
Image control on Forms causes Access to crash
Access crashing when flipping through the records fast
Must picture loading finish before changing records?
Rapid record scrolling (navigation buttons) crashing
loading of external pictures into form
Image Control 'out of stack space' problem
Must picture loading finish before changing records?

The "Scroll-too-Quick" Crash:
If you use an Access Image Control on a form to display an image for each record, the image control can cause Access to crash if you scroll quickly between records. The problem occurs when starting to load a new image (by setting the 'Picture' property) while the 'Loading Image' dialog is still displayed for the previous record's image.

The error can appear in a variety of ways. You may see "Illegal operation" (Windows 95) or a "Dr. Watson" (Windows NT), "General Protection Fault" (GPF), or "Out Of Stack Space". You may see something like the error below, or nothing at all (Access just disappears).

MSACCESS.exe Exception: access violation (0xc0000005)
Address: 0x0378c6b0

Fixing the problem requires a registry tweak to suppress the "Loading Image" dialog. For full details see the article: Hide the Loading Image dialog

Related Articles

Run-Time error '2114' Microsoft Access doesn't support the format of the file
Slow Form Navigation and Record Scrolling
Hide the Loading Image dialog ("Importing" message)

Imaging for Access that's Easy, Efficient & Fast
  • NO OLE Bloat
  • NO App Dependencies
  • NO Complex Coding
  • NO Performance Penalty
  •  DBPix logo
    Read More

    Microsoft and the Office logo are trademarks or registered trademarks of Microsoft Corporation in the United States and/or other countries.