I know that storing images in a database is oftern a bad idea.
However there can come requirements that force things on you.

For the database end I have used an IMAGE datatype in SQL Server.

The delphi approach is as follows:

You need to use GraphicEx to allow display in the normal controls.
All this requires is adding the GraphicEx unit to the end of your uses clause.

procedure LoadJPEGImageFromStream(const aImage: TImage;
  const stream: TStream);
var
  aJPEG : TJpegImage;
begin
    aJPEG := TJPEGImage.Create;
    try
      aJPEG.LoadFromStream(stream);
      aImage.Picture.Assign(aJPEG);
    finally
      aJPEG.Free;
    end;
end;

 

procedure LoadFromDB(Image : TImage; aField : TBlobField)
var
  aBLOBStream : TStream;
begin
  ado.Open;
  ado.First;

  aBLOBStream := adoFAX.CreateBlobStream(aField,bmRead);
  try
    LoadJPEGImageFromStream(Image, aBLOBStream );
  finally
    aBLOBStream.free;
  end;

end;
 

procedure SaveToDB(const filename : string)
var
  FS : TFileStream;
begin
  FS := TFileStream.Create(filename, fmOpenRead);
  try
    ado.open;
    ado.Insert;
    adoIMAGE.LoadFromStream(FS);
    ado.Post;
  finally
    FS.Free;
  end;
end;
 

Just to check that this is not a Delphi-only format I wrote the following test from C#:

            sqlDataAdapter1.Fill(dataSet11, “DB”);
            // How to get an image from a database in .NET                   
            pictureBox1.Image = new Bitmap( new MemoryStream( dataSet11.DB[0].IMAGE ) );
            pictureBox1.Height = pictureBox1.Image.Height;
            pictureBox1.Width = pictureBox1.Image.Width;
 

This loads the image previously stored by a Delphi app.

This ensures that the image format used is language neutral. 

There are a number of reasons why a feature is added to a software product:

– Customer requested feature

– Company considers this will benefit the customer 

– To obtain a sale that would not otherwise be made

– Match a competitor

– To qualify for an award 

 

 

This is link to a microsoft knowledge basis article covers auidting under active directory.

This may help identify least priv problems. 

The latest incarnation of Delphi (the tenth version) 2006 seems to be way beyond the microsoft contribution to the field. Out of the box it provides a massive component suite and extensive refactoring tools.

 

I have just upgraded a large Delphi 5 application suite to D2006 with very little pain.

A few objects had moved units, I had to add the variants unit in a lot of places. Some of the MIDAS parameters now expect TCustomClientDataSet rather than TClientDataset.

 It is impressive in that I was able to interchange COM clients and servers build with the differing versions without much trouble. In fact the code areas which we had used the built in events the least required fewer or no changes.

 A minor annoyance is that the TChart was missing from the QuickReports 4 suite.

TeeChart is an amazing chart control suite.