Can I make an employee info database with a photo in Access?

G

GeronT

I need a fairly detailed database on employees that has a headshot of each
employee that shows up with their record. Is this best done in Access or in
something else?

It would be nice if I could embed a link to a larger photo for printing
purposes too. Also I'd like to be able to put it into PDAs as well so the
data is portable. Any ideas would be helpful.

Thanks,
John
 
M

Mike Painter

GeronT said:
I need a fairly detailed database on employees that has a headshot of
each employee that shows up with their record. Is this best done in
Access or in something else?
Click to expand...

I have a field on my form which contains the location of the picture I want
and in the OnCurrent event of the form I have:

Private Sub Form_Current()
On Error Resume Next
Me![EmployeePhoto].Picture = Me![pictureloc]

End Sub

In my case I don't care if the picture is there or not.

I also have routines that use Dir() to loop through the folder where the
pictures are and place that location (C:\Somefolder\Somepicture001.mpg)
in both pictureloc and the persons name.
It only adds new pictures.
Then I can go through and fill in the rest of the data.

Picture size is unimportant since you can make the photos fit.

Portability is another issue.
 
L

Larry Linson

I need a fairly detailed database on
employees that has a headshot of each
employee that shows up with their record.
Is this best done in Access or in
something else?
Click to expand...

"Best" like "beauty" is most often "in the eye of the beholder". However you
can do a detailed database in Access, and that database can include images.
Access databases can be organized to be used by multiple users. They can
even be the client to any ODBC-compliant server database. Here's a little
more on using imgages:

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