pictures in tables?

[Talal Itani]

Hello,

This is the first time I use a database program. I am trying to build a
product database. Each product will have an ID number, a description, and a
photograph. I need the table to display the photographs of the items, so
that I can visually spot the item that I am looking for. Please let me know
if it is possible to have pictures in the tables, and if not, what should I
do? Maybe Access is the wrong tool for this task. Maybe one form screen
can have multiple products. Please give me your recommendations.

Thanks.

 

[Larry Linson]

This is the first time I use a database program. I am
trying to build a product database. Each product will
have an ID number, a description, and a photograph. I
need the table to display the photographs of the items, so
that I can visually spot the item that I am looking for.
Please let me know if it is possible to have pictures in
the tables, and if not, what should I do? Maybe Access
is the wrong tool for this task. Maybe one form screen
can have multiple products. Please give me your
recommendations.

Note that the suggestions in the referenced examples do require minimal
understanding of VBA programming, but also note that we are told that Access
2007 has eliminated the problem of database bloating with storing and
displaying pictures as OLE Objects (which is the only convenient way to show
multiple images on-screen, using continuous forms view). When Access 2007 is
released to the public, and the requisite number of Service Packs and
hotfixes have been issued to get it past it's "juvenile system" problems,
that may be your solution -- reduced "programming" and no bloating.

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.

Larry Linson
Microsoft Access MVP

 

[Thorsten Stegner]

If you use the fieldtype "ole" you are able to insert pictures and use them.

 

[Larry Linson]

"Thorsten Stegner" wrote

If you use the fieldtype "ole" you are able to insert pictures and use
them.

And, if you are using an earlier version than Access 2007, you subject
yourself to significant, unavoidable database bloat. And, no matter what
version, you subject yourself to the [features and functions | whims and
fancies | vagaries and inconsistencies] of whatever software the user has
registered for the image file type.

Larry Linson
Microsoft Access MVP

 

[aaron.kempf]

bloat is avoidable you fat ****ing lazy retard

just use Access Data Projects

-Aaron

"Thorsten Stegner" wrote

If you use the fieldtype "ole" you are able to insert pictures and use
them.

And, if you are using an earlier version than Access 2007, you subject
yourself to significant, unavoidable database bloat. And, no matter what
version, you subject yourself to the [features and functions | whims and
fancies | vagaries and inconsistencies] of whatever software the user has
registered for the image file type.

Larry Linson
Microsoft Access MVP

 

[aaron.kempf]

with SQL Server you have your choice of two different data types for
this; if you're storing SVG then you could probably store it as raw XML
and have GREAT performance

-Aaron

"Thorsten Stegner" wrote

If you use the fieldtype "ole" you are able to insert pictures and use
them.

And, if you are using an earlier version than Access 2007, you subject
yourself to significant, unavoidable database bloat. And, no matter what
version, you subject yourself to the [features and functions | whims and
fancies | vagaries and inconsistencies] of whatever software the user has
registered for the image file type.

Larry Linson
Microsoft Access MVP

 

[rebelscum0000]

Talal,

I use an active X DBPix
you can find it
at ammara dot com

Is expensive but for newbies is a great tool

I have Access 2002 with SP3, I will not wait until Access 2007 is
released to the public

The beta of Access 2007? Never Mind in full of bugs and spywares
Also Office 2007 is going to be very expensive, and still wait for the
First Service Pack???

Regards,
Antonio Macias
Mexico City

 

[Larry Linson]

bloat is avoidable you fat ****ing lazy retard

just use Access Data Projects

I've used ADP with SQL Server. Overall, I could not see that it was any
better, perhaps not even as good as MDB-ODBC-Server, and ADP doesn't work
with most of the server DBs I've used over the years -- its server support
is only for MS SQL Server.

Bloat is avoidable, even with Jet, even with MDB -- but not with images
stored as OLE Object, in Access 2003 and earlier. One of the improvements
in Access 2007 ACCDB is that they did away with image-in-OLE bloat.

Larry

 

[george_w_blair]

Store the images as files (in a folder). Just store a reference to the
location of the image in the database.

George

 

[John Vinson]

Store the images as files (in a folder). Just store a reference to the
location of the image in the database.

George

Just FWIW, the newly released Access2007 is apparently MUCH improved
for picture handling. Bloating is greatly reduced, and you can much
more easily use pictures in continuous forms, etc.

George's suggestion is quite apropos for earlier versions, but Talal,
if you have A2007 (or can upgrade to it), it's worth a try.

John W. Vinson[MVP]