Stephan
Please let me respond to your critique and hopefully help Bob along the way
First, thanks for your response to these comments
Please read on to your suggestion number 5, were you will find my hooray that you have solved my problem!! However, please give us suggestions on your point number 4 (changing the registry OR ‘Suppress the "Loading Image" dialog’
Thanks a million
Ro
Bob – best of success in your picture adventure
----- Stephen Lebans wrote: ----
Ron if you have spent two months with this issue then I would sugges
that you need to go back and revisit the suggestions given to yo
earlier. THis should have been a one day issue at most
I would have loved to have solved this issue in one day. I have attempted to apply all the suggestions that you and others gave. Some of the suggestions were undoubtedly beyond my limited understanding of coding. I am a rancher and a retailer, not a database expert
Keeping the Images in a folder instead of the MDB is certainly th
suggested course of action. Since you are still using Access97, which i
now 3 full versions out of date, you have to expect you may run into th
type of memory/resource issue you are encountering
Is the latest version of Access improved in this area - other than than offering 2MB of space?
Here are some steps you must follow to eliminate/reduce the error yo are encountering
1) Defrag your Hard drive. The temp printer output files Acces
generates can be very large when they contain images
I regularly defrag my hard drives
2) Make sure the drive you point your Virtual Memory Manager to ha
several hundred MB's of free space
I allow WindowsXP to manage the memory allotted, and the 20GB hard drive I use has 8 GB of free space
3) If you are still using Win9x then make sure you reboot befor
printing
I use MS WindowsX
4) You must turn off the "Loading Image" dialog via the Registr
solution here
http://www.mvps.org/access/api/api0038.ht
I did change the registry entry to NO and it did not change anything (sure wish you could give further advice on this)
HKEY_LOCAL_MACHINE\Software\Microsoft\ Shared Tools\Graphics Filters\Import\JPEG\Option
Change the ShowProgressDialog key value to "No"
5) Load the Images into the Image control from the Detail Section'
Print event NOT THE FORMAT EVENT
This is hopefully the MOST important thing I have learned in this discussion.
THIS FIXED MY PROBLEM!!!!! The slow scrolling through every picture and the slow printing problem is fixed!!!!!!!!!!!!
If you follow the above steps and your Report still fails then here ar
a couple of more solutions
1) Upgrade to the latest version of Windows at the very least. Bette
yet, upgrade to Access 2003 as well
o
2) Use the PrintOUt method to only print out a limited number of page
at a time. Repeat as required
o
3) THis solution seems to look after most of the memory issues. A
runtime convert the Images to Bitmap format prior to loading them int
the Image control. Here is some sample code
From: Stephen Lebans (
[email protected]
Subject: Re: Images in Report
View: Complete Thread (18 articles
Original Forma
Newsgroups: microsoft.public.access.report
Date: 2002-09-16 18:46:39 PS
Bruce I finally got a chance to test your method last night. It helpe
but only with the actual printing and not the Print Preview itself
I was able to print the failed Report directly to the printer or to
disk printer file so that's great! Don't get me wrong, it's still a goo
thing because at least you can print the report
Unfortunately Acess still runs out of resources when you page back an
forth through Print Preview
I plan to spend some time onthis issue shortly
Here is the code I use to convert any Jpeg, Gif, or Metafile into a BMP
Rather than using one of my API solutions I have cheated and set a
Reference to Standard OLE Types type library in order to get at the
SAVETODISK method. But no ActiveX controls are required
Private Sub Detail_Print(Cancel As Integer, PrintCount As Integer)
Private ctr As Long
ctr = ctr + 1
Select Case ctr
Case 1
Me.Image10.Picture = CreateBitmapFile("C:\A.jpg")
Case 2
Me.Image10.Picture = CreateBitmapFile("C:\b.jpg")
Case 3
Me.Image10.Picture = CreateBitmapFile("C:\c.jpg")
ctr = 0
Case Else
ctr = 0
End Select
End Sub
Private Sub Report_Open(Cancel As Integer)
ctr = 0
End Sub
Private Function CreateBitmapFile(fname As String) As String
Dim obj As Object
Set obj = LoadPicture(fname)
If Not IsNull(obj) Then
SavePicture obj, "C:\SL11-52"
DoEvents
End If
CreateBitmapFile = "C:\SL11-52"
Set obj = Nothing
End Function
--
HTH
Stephen Lebans
http://www.lebans.com
Access Code, Tips and Tricks
Please respond only to the newsgroups so everyone can benefit.
============================================
NMex Ron said:
I sent this yesterday -- but it was not posted, so I will try again:
2-19-2004
Bob,
I hope you get an answer to your question.
your entire database will stop working when you get about 100 pictures
'linked'. The error message is "Database has reached maximum size".
In Access97 this is 1GB, Access 2000 2GB (200 pictures).
However, this is what I have learned:
"...., as well as 'linking' to the original file, a 'Preview' image is
stored in the database. Since this image is uncompressed it can be up
to 100 times the size of the original image file (or more), hence the
problem you are seeing."databases, and finally not linking the photos but only storing the text
description of the path to the photo file in the database (as suggested
by all the 'experts'). This works okay in 'FORMS', but when trying to
view or worse yet print a REPORT, the database locks up and 'times-out'
while attempting to format the reports with the pictures.am trying some others as well):
