Re: Handling pictures with DBI and Access

[wardk]

I really agree with AidanLee. You may want to just stay away from saving blob data. It's my bias (but it's an educated bias) against Access, but it seems that doing blobs is gonna eventually see performance issues as the access db grows (my experience is big access tables are trouble). Not to mention portability issues (when you toss the yoke and move to mySql or another RDBMS).

I would use some standard naming that makes matching thumnails to their big brothers intuitive and easy to code for, then perhaps store the name/path info in the db, and just say no to stuffing images into blobs....even if NOT using MS Access, images do just fine sitting in a file structure and reading them from the file system is going to be much more efficient that having Access between you and the files.

...and using any manual process above and beyond the minimal seems like too much work, then again perhaps perl is just making me lazy ;-)

good luck whichever way you go!

[kevin_i_orourke]

I think the original decision to store the image data in Access was probably false laziness.

I wanted the picture to be displayed within an Access form and this seemed like the easiest way to do that. I'm sure (given a bit of VB code) I could load an image from the filesystem into a form.

Must port to MySQL soon, it's approaching the top of the things to do list.

Kevin O'Rourke