Re: bound object frame: picture

From: NMex Ron (anonymous_at_discussions.microsoft.com)
Date: 02/22/04 

Date: Sat, 21 Feb 2004 19:11:06 -0800

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!
Ron

Bob – best of success in your picture adventure.

     ----- Stephen Lebans wrote: -----
     
> Ron if you have spent two months with this issue then I would suggest
     that you need to go back and revisit the suggestions given to you
     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 the
     suggested course of action. Since you are still using Access97, which is
     now 3 full versions out of date, you have to expect you may run into the
     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 you
     are encountering:
> 1) Defrag your Hard drive. The temp printer output files Access
     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 has
     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 before
     printing.
I use MS WindowsXP

> 4) You must turn off the "Loading Image" dialog via the Registry
     solution here:
     http://www.mvps.org/access/api/api0038.htm
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\Options
Change the ShowProgressDialog key value to "No".

> 5) Load the Images into the Image control from the Detail Section's
     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 are
     a couple of more solutions:
     
     1) Upgrade to the latest version of Windows at the very least. Better
     yet, upgrade to Access 2003 as well.
      or
     2) Use the PrintOUt method to only print out a limited number of pages
     at a time. Repeat as required.
     or
     3) THis solution seems to look after most of the memory issues. At
     runtime convert the Images to Bitmap format prior to loading them into
     the Image control. Here is some sample code:
     
     
     From: Stephen Lebans (StephenLebans@mvps.org)
     Subject: Re: Images in Reports
     View: Complete Thread (18 articles)
     Original Format
     Newsgroups: microsoft.public.access.reports
     Date: 2002-09-16 18:46:39 PST
     
     
     Bruce I finally got a chance to test your method last night. It helped
     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 a
     disk printer file so that's great! Don't get me wrong, it's still a good
     thing because at least you can print the report!
     
     Unfortunately Acess still runs out of resources when you page back and
     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" <emial to: rrrlonghorns@hotmail.com> wrote in message
     news:68825CCF-A149-45DF-A1A9-B9426D6FA6C1@microsoft.com...
> 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.
>> I have been trying to get an answer on the same basic subject for
     about two months now.
>> Warning: If you follow the Northwind sample an link the pictures,
     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).
>> I thought 'linking' would keep the photo 'out of the database'
     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."
>> I have tried splitting the database, linking tables from additional
     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.
>> This is a link to the MS solution (Works with the results I described
     above):
>> http://support.microsoft.com/default.aspx?scid=kb;en-us;210100
>> Here are the subjects of the 'threads' I have posted on this forum (I
     am trying some others as well):
> How do I correctly write this expression?
> Photo Paths
> LoadSaveJpeg
>> Best of luck - (maybe no photo?)
> Ron
>

Relevant Pages

  • Re: how to count total number of images in the database
    ... Ronie Samuels wrote: ... stored in the database. ... images are in format, ...
    (comp.soft-sys.matlab)
  • Re: Surrogate Keys: an Implementation Issue
    ... a database that must provide a complete audit trail of every change. ... The SSN is a surrogate that works most of the time. ... Unless the key is immutable, when Bob issues the update, ... by a logical identifier. ...
    (comp.databases.theory)
  • Re: Surrogate Keys: an Implementation Issue
    ... a database that must provide a complete audit trail of every ... when Bob issues ... identified by a logical identifier. ... Do Jane Jones and Jane Smith represent different people? ...
    (comp.databases.theory)
  • Re: [PHP] Re: how to display images stored in DB*
    ... Your claim is that in ALL cases using a file system to store images ... bitmaps in a database without a damn good reason, a bad practice, yes. ...
    (php.general)
  • Re: [PHP] Re: how to display images stored in DB**
    ... for storing images is "bad" practice. ... "Bad" practice or "good" practice depends upon the needs and one's perspective of the situation. ... If you were to talk to the average computer user; or to the average investor who invests in technologies; or to the businessman who is paying the bills for programmers to build the product while trying to make money at the same time; they all might have different opinions as to the quality and state of software. ... If you assume that you have one database supply all the images to all ...
    (php.general)