Printing An Image !

Collapse
This topic is closed.
X
X
 
  • Time
  • Show
Clear All
new posts
  • Prakash

    #1

    Printing An Image !

    I'm developing an HR package which would contain the Employees Photo +
    upto 3 pages (pictures) of his Passport + pictures of his Driving
    License and Residence Card.

    If the user wants to print the Passport Copies, Driving License,
    Residence Card, etc. what is the best method to accomplish this ?

    Best Rgds,
    Prakash.

  • Larry Linson

    #2
    Re: Printing An Image !

    "Prakash" <simran@omantel .net.omwrote
    I'm developing an HR package which would contain the Employees Photo +
    upto 3 pages (pictures) of his Passport + pictures of his Driving
    License and Residence Card.
    >
    If the user wants to print the Passport Copies, Driving License,
    Residence Card, etc. what is the best method to accomplish this ?
    (1) Are you asking basic advice on the form in which to store the images,
    and, then, how to handle them; or (2) have you already decided how to store
    them, and just want to know how to print them. (3) Do you mean print them in
    a Report, or print them individually, or ??? And, helpful but perhaps not
    absolutely essential, (4) by "up to," do you mean the number of images may
    vary from employee to employee?

    The answers to the first question is absolutely needed to respond.

    If the answer to the second question is "Yes," then you need to give details
    on how you plan to store the pictures.

    The answer to the third question is a matter of your "requiremen ts" -- what
    do you need, not something we can answer.

    And, as I said, the answer to the fourth question will be helpful.

    Larry Linson
    Microsoft Access MVP


    Comment

    • Prakash

      #3
      Re: Printing An Image !

      Hi Larry !! I'm sorry, I guess I was a bit too ambiguous. Here goes :
      (1) Are you asking basic advice on the form in which to store the images,
      and, then, how to handle them;
      1) No ! At the moment I haven't as yet embarked on the project & so
      don't want to know about the forms. I guess as & when I encounter any
      problems, I'll post here.

      or (2) have you already decided how to store
      them, and just want to know how to print them.
      Yes ! I have decided to use a "link" to the images rather than
      embedding them into my database especially as passport pages for all
      employees could greatly increase the size of the database. If I've
      chosen wrongly, please feel free to correct me. As it stands, I plan to
      store all the images in a folder & then provide a link to them.

      (3) Do you mean print them in
      a Report, or print them individually, or ???
      I'm planning on having a command button with the following captions:
      Print Passport - Pg1
      Print Passport - Pg2
      Print Passport - Pg3
      When the user clicks these buttons the header on the page should be:
      Employee Name ... Passport Copy - Page 1 (and so on)

      (4) by "up to," do you mean the number of images may
      vary from employee to employee?
      No !! A provision of 3 image links will be provided ... one for each
      Passport Page.
      Of course it's possible the user may have provided a link to the image
      or left it blank.


      I hope I'm going about it in the right way. Please do steer me in the
      right direction if you feel otherwise.

      Thx & Best Rgds,
      Prakash.






      Larry Linson wrote:
      "Prakash" <simran@omantel .net.omwrote
      >
      I'm developing an HR package which would contain the Employees Photo +
      upto 3 pages (pictures) of his Passport + pictures of his Driving
      License and Residence Card.
      >
      If the user wants to print the Passport Copies, Driving License,
      Residence Card, etc. what is the best method to accomplish this ?
      >
      (1) Are you asking basic advice on the form in which to store the images,
      and, then, how to handle them; or (2) have you already decided how to store
      them, and just want to know how to print them. (3) Do you mean print them in
      a Report, or print them individually, or ??? And, helpful but perhaps not
      absolutely essential, (4) by "up to," do you mean the number of images may
      vary from employee to employee?
      >
      The answers to the first question is absolutely needed to respond.
      >
      If the answer to the second question is "Yes," then you need to give details
      on how you plan to store the pictures.
      >
      The answer to the third question is a matter of your "requiremen ts" -- what
      do you need, not something we can answer.
      >
      And, as I said, the answer to the fourth question will be helpful.
      >
      Larry Linson
      Microsoft Access MVP

      Comment

      • Larry Linson

        #4
        Re: Printing An Image !

        "Prakash" <simran@omantel .net.omwrote
        >(1) Are you asking basic advice on the form
        >in which to store the images, and, then, how
        >to handle them;
        >
        1) No ! At the moment I haven't as yet embarked
        on the project & so don't want to know about the
        forms. I guess as & when I encounter any
        problems, I'll post here.
        I apologize for my question being confusing. I used "form" not in terms of
        an Access Form, but meaning the format, type of file, etc. for storing the
        pictures.
        >or (2) have you already decided how to store
        >them, and just want to know how to print them.
        >
        Yes ! I have decided to use a "link" to the images rather
        than embedding them into my database especially as
        passport pages for all employees could greatly increase
        the size of the database. If I've chosen wrongly, please
        feel free to correct me. As it stands, I plan to store all
        the images in a folder & then provide a link to them.
        Later, I'll include a reference to samples and an article. There are
        considerations to balance... if the images are stored separately in
        directories, it is more likely that one or some (or, worse, all) of them
        might be accidentally deleted. If they are stored in the DB as OLE Objects,
        through Access 2003, there is bloat (see the referenced article for "why").
        We are told that Microsoft has eliminated that bloat in Access 2007, but
        there are a few other "consequenc es" of using the OLE Object and Bound OLE
        Frame.
        >(3) Do you mean print them in
        >a Report, or print them individually, or ???
        >
        I'm planning on having a command button with the following captions:
        Print Passport - Pg1
        Print Passport - Pg2
        Print Passport - Pg3
        When the user clicks these buttons the header on the page should be:
        Employee Name ... Passport Copy - Page 1 (and so on)
        I'm not sure why you would print the pages individually. If there's no
        compelling reason to do otherwise, you could just print one report, that
        includes all three pictures (if available).
        >(4) by "up to," do you mean the number of images may
        >vary from employee to employee?
        >
        No !! A provision of 3 image links will be provided ... one
        for each Passport Page. Of course it's possible the user may
        have provided a link to the image or left it blank.
        So, seems to me the answer is "Yes -- there should be three images, but it's
        possible that the user may have omitted a link." Do you want to print a
        blank page if there are only two images?

        Larry Linson
        Microsoft Access MVP



        Comment

        • Larry Linson

          #5
          Re:Image DB Example, WAS Printing An Image !

          The sample imaging databases at http://accdevel.tripod.com illustrate three
          approaches to handling images in Access, and the download includes an
          article discussing considerations in choosing an approach. Two of the
          approaches do not use OLE Objects and, thus, avoid the database bloat, and
          some other problems, associated with images in OLE Objects.

          If you are printing the images in reports, to avoid memory leakage, you
          should also see MVP Stephen Lebans' http://www.lebans.com/printfailures.htm.
          PrintFailure.zi p 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.

          Larry Linson
          Microsoft Access MVP


          Comment

          Working...