Access bombs if report pages to fast

  • Thread starter Thread starter OceansideDJ
  • Start date Start date
O

OceansideDJ

My report changes the Picture file name of an image control on event On
Current. The source is one of many jpg files. If I page too fast through the
report pages, Access quits.

Is there a way to make Access wait for the image to update, or to go to the
next page without fouling on the image?

Thanks,
Mike
 
You should spend few minutes searching in GoogleGroups to fully
understand all of the issues involved here as there are several.
Here's a couple of items to get you heading in the right direction.

1) Turn off the "Loading Image" dialog that appears as each Jpeg is
loaded into the Image control. Use the Registry solution bere:
http://www.mvps.org/access/api/api0038.htm

2) Convert the Jpegs to Bitmaps prior to loading the images at runtime.
There is code here showing you how to do this easily.
http://www.lebans.com/printfailures.htm
PrintFailure.zip is an Access97 MDB containing a report that fails
during the Access formatting process prior to being spooled to the
Printer Driver.
This MDB also contains code showing how to convert the contents of the
Image control to a Bitmap file prior to printing. This helps alleviate
the "Out of Memory" error that can popup when printing image intensive
reports.

3) Upgrade to the latest version of WIndows

4) Upgrade to the latest, well at least A2K2 version of Access.

--

HTH
Stephen Lebans
http://www.lebans.com
Access Code, Tips and Tricks
Please respond only to the newsgroups so everyone can benefit.
 
Stephen,
Thanks. I tried it on a faster machine with WinXP and Access 2000, and no more
crashes. I will try your other suggestions to make it work on the older,
slower NT4 machine.

Mike
 
Back
Top