photo field

[Faisal]

Dears

I was about to make a data base for emplyess details
my table stucture like this respectivly-Emplyee id,Emplyee Name,Date of
birth,Section
now i want to add one more field to store emplyess photos,how it is possible

Can you any body sujest any logic to achive this

my thanks in advance

Regards
Faisal
Riyadh

 

[aaron.kempf]

Add a field with the datatype OLE Object.

Create a form on this field; and presto-chango; you can drag and drop
pictures into a database.

-Aaron

 

[BruceM]

Storing more than a few images in a table will soon cause the database to
become too large. For alternative techniques see this article:
http://www.mvps.org/access/forms/frm0030.htm

 

[aaron.kempf]

when your database is bloated-- move to SQL Server

 

[Larry Linson]

Storing more than a few images in a table will soon
cause the database to become too large. For
alternative techniques see this article:
http://www.mvps.org/access/forms/frm0030.htm

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.zip 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.

And, Stephen has an ActiveX control available that works in cases where the
graphics filters are not available -- and works better, I've heard, than the
OLE Object and OLE Controls.

Please note that there are other approaches, e.g.,
Application.FollowHyperlink, but those, like OLE and Bound OLE Frames (which
from the symptoms you describe, are what you were / are using) still leave
you "at the mercy of the imaging software registered for the filetype").

Finally, Access 2007 has enhancements that, reputedly, eliminate the
database bloat long associated with OLE Objects and Bound OLE Frames. But,
it still leaves you relying on the software registered for the image type,
which may not be as "cooperative" as we'd like in creating our display. It
also has the capability of having a variable number of Attachments to a
Record, which may be helpful. But, as I have not done much with it yet, I
certainly wouldn't suggest you rush out and replace an earlier version --
not until the first Service Pack, at least.

Larry Linson
Microsoft Office Access MVP