How to programetically embed an ole bitmap in a database field

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

    How to programetically embed an ole bitmap in a database field

    I need to find a way of embedding an ole object into a database field, so it
    can be retrieved by a Crystal report and displayed as a picture.

    Embedding the bitmap file as a long binary or a blob is easy, but this can
    not be interpreted as an ole object and hence not displayed on the report.

    Any suggestion would be very welcome.


  • oj

    #2
    Re: How to programetically embed an ole bitmap in a database field

    sql does not store embedded object. You will have to stream the blob to a
    file and use that file in your report.

    --
    -oj
    Rac v2.2 & QALite!



    "Kevin Holland" <kevin_holland@ hotmail.com> wrote in message
    news:OwrtBF6jDH A.1740@TK2MSFTN GP12.phx.gbl...[color=blue]
    > I need to find a way of embedding an ole object into a database field, so[/color]
    it[color=blue]
    > can be retrieved by a Crystal report and displayed as a picture.
    >
    > Embedding the bitmap file as a long binary or a blob is easy, but this can
    > not be interpreted as an ole object and hence not displayed on the report.
    >
    > Any suggestion would be very welcome.
    >
    >[/color]


    Comment

    • oj

      #3
      Re: How to programetically embed an ole bitmap in a database field

      sql does not store embedded object. You will have to stream the blob to a
      file and use that file in your report.

      --
      -oj
      Rac v2.2 & QALite!



      "Kevin Holland" <kevin_holland@ hotmail.com> wrote in message
      news:OwrtBF6jDH A.1740@TK2MSFTN GP12.phx.gbl...[color=blue]
      > I need to find a way of embedding an ole object into a database field, so[/color]
      it[color=blue]
      > can be retrieved by a Crystal report and displayed as a picture.
      >
      > Embedding the bitmap file as a long binary or a blob is easy, but this can
      > not be interpreted as an ole object and hence not displayed on the report.
      >
      > Any suggestion would be very welcome.
      >
      >[/color]


      Comment

      Working...