Photos into access

  • Thread starter Thread starter firecop1
  • Start date Start date
F

firecop1

I am currently using an Access database (2002-3) with a front and backend. I
am at a point now where I need to start storing photos which is new to me.

I understand that I have to create a field somewhere as an OLE object but at
that point I am lost. I created the field in my backend (where the tables
reside) and then placed the field on a form but thats all I have I cant seem
to use the field...

can anyone help>?

Thanks
 
The general answer to this one is don't store the photo's in your database.
Storing photo's within the database will cause massive bloating problems
with your backend, and is to be avoided at all costs.
The best way to achieve what you want, is to have a directory where your
photos will be stored seperately, and have a field in your database that will
store the loaction of those photo's.

I had to do exactly what you want a few weeks ago, and with a little digging
around on groups.gooogle.com I managed to find enough information to build a
picture handler which works pretty well.

The whole code etc is too big to post on here, but if you want me to e-mail
it to seperately then contact me through my website and I'll gladly send it
to you.

HTH

Neil
www.nwarwick.co.uk
 
The general consensus in these (access) newsgroups is that storing images in
your Access data tables is not a good idea. The reason given is that this
causes the database to bloat.

The discussion of where to store images and pros/cons generally is left out.
The same discussion can be used to decide whether to store images in ANY
backend data store (i.e., Access JET, SQL-Server, ...). The size of the db
and any "bloat" issues are given as reasons not to do so.

On the "pro" side, managing a file directory full of images, handling
"missing" files, and security are reasons to consider putting the images
into the database, rather than storing as separate image files.

On the third hand, either way you do it, you'll still need to pay the "cost"
of moving all those bits back and forth between the front-end on your PC and
the back-end on your network ... you DID split your database, right?!
 
Yes the database is split. Problem is that the DB is on multiple computers
and this information is critical (database is for the fire chiefs to view
building information while responding to calls including seeing what the
building looks like).

storing the photos in a seperate file is ok but that means each computer has
to be updated each time i add pictures and I have to make sure that no file
names or paths are accidentally changed.

I have been using filemaker in the interim but really need to make this work
in access.
 
firecop1 said:
Yes the database is split. Problem is that the DB is on multiple computers
and this information is critical (database is for the fire chiefs to view
building information while responding to calls including seeing what the
building looks like).
Click to expand...

I'm not clear on what you mean when you say "the DB is on multiple
computers"? If the information in your database is critical (life/death)
and/or sensitive (could be mis-used by the wrong folks), I hope you have
also considered the robustness and security of your design.
storing the photos in a seperate file is ok but that means each computer has
to be updated each time i add pictures and I have to make sure that no file
names or paths are accidentally changed.
Click to expand...

That's related to one of the issues I mentioned. But your description
sounds like you are trying to place the photos on each local computer. I
don't know your network topology, but it would seem like less work to have
each desktop PC look to the same, shared network location for the photo(s).
I have been using filemaker in the interim but really need to make this work
in access.
Click to expand...

What is it about Access that led you to decide on it? Have you considered
using the rapid development features of Access as a front-end to a different
back-end data store?

Good luck!

Jeff Boyce
 
If you use the built-in OLE Embedding capability (eg using the bound OLE Frame) there is typically an overhead
of up to 100 *times* for storing jpeg images. There are also other common issues, such as configuration
problems (particularly on Access/Office 2003).

It is quite possible to store images in tables without this overhead, loss or most of the other problems
associated with OLE Embedding, but this typically either requires considerable code or a 3rd party component.


More info about the problems, and links to solutions (commercial and free/code-based) are available here:

http://www.ammara.com/articles/accesspictureole.html

and here:

http://www.ammara.com/articles/imagesaccess.html

Among the solutions is our own component, DBPix, which was recently chosen by one US city for its property
database which is used to help fire crews locate and identify properties faster.
 
What version of Access do you use?

You say the DB is on multiple computers. Are these computers connected to a
network?

Are the computers connected to the internet?
 
Back
Top