DEFINITELY keep the photos outside of your database and only keep a link to them within table/s in the database. Storing photos (etc) in a database itself will cause the most SEVERE case of "database bloat" which can cause all sorts of problems. Also allows for the photo itself to be updated/altered "outside" of the database (which may not necessarily be approprate in your case)
You definitely CAN store your photos inside the database without bloating the MDB file, but you will need a supplementary programm (I think it costs 150$ or so). Have a look "
I use this wizard (very easy to use) since more than 12 months now for JPGs, in particular for web applications. The JPGs are displayed via ASP and it is very fast.
This site uses cookies to help personalise content, tailor your experience and to keep you logged in if you register.
By continuing to use this site, you are consenting to our use of cookies.