Lets talk databases!

[Monster Dave]

Hey Guys and Gals!

I need some assistance with a database related idea.

I built an inventory database system for our office which allows us to track and order office and medical supplies when needed. Recently, I decided that I'd like to associate an image with each item in the database. Ultimately, the goal is for upon performing a lookup for an item, that along with pricing and item information, that also an image of the item is displayed as well.

This is something that I've never tried to do before, but wanted to see if anyone had an idea how to do that. I'm using MS Access 2007.

Thanks!

[Ontario_Monster]

See if you can't use LOB Large objects in MS Access, I know you can in larger databases Oracle etc.  If not the next alternative is to just store a link to a picture of the item so people can look it up if they have too.  For the link if you use single storage location and make sure there are no spelling mistakes.

cheers

[Monster Dave]

humm....


I'd rather not use a link if I can avoid it - takes away from the "magic" of what the system can do.

I'll see if I can do something with LOB.

Thanks!




Other ideas??

[derby]

http://office.microsoft.com/en-us/access-help/store-images-in-a-database-HP005280225.aspx

[Monster Dave]

Now why hadn't I thought to look to Microsoft for the answer....




Thanks. 

[ducatiz]

One thing to note is that ACcess stores the image as a BMP which will inflate the size of the database -- no compression format.

If you use small images or a standard size with a reduced palette you might be able to control it a bit. 

[Monster Dave]

One thing to note is that ACcess stores the image as a BMP which will inflate the size of the database -- no compression format.

If you use small images or a standard size with a reduced palette you might be able to control it a bit. 

That's a really good point. Especially since I'm planning on using it for a LOT of items.

[ducatiz]

That's a really good point. Especially since I'm planning on using it for a LOT of items.

I use this fun little photo program called Paintshop Pro which has a macro function -- so you can automate shrinking and converting photos if you want.  I did it once for a catalog a friend made -- converted all her pics to 64 pix high and only 32 colors in the palette.  This shrunk the per-image size to around 3k

[Monster Dave]

I use this fun little photo program called Paintshop Pro which has a macro function -- so you can automate shrinking and converting photos if you want.  I did it once for a catalog a friend made -- converted all her pics to 64 pix high and only 32 colors in the palette.  This shrunk the per-image size to around 3k

I've got this nifty little suite called CS5 that may do something along those lines...

[ducatiz]

I've got this nifty little suite called CS5 that may do something along those lines...

Suiiiite

[Fresh Pants]

Suiiiite

[sugarcrook]

I thought you were asking about databases, not Access.   

[Monster Dave]

I thought you were asking about databases, not Access.   

OH SNAP!! 

[ab]

If you have multi-users , then you will hate access due to locking issues when many users are accessing rows located nearby.  Page level locking, table level locking , row level lockings are issues to think about.
If you can swing it, why not use SQL Server and write an aspx web form or even better MVC framework.

[Monster Dave]

If you have multi-users , then you will hate access due to locking issues when many users are accessing rows located nearby.  Page level locking, table level locking , row level lockings are issues to think about.
If you can swing it, why not use SQL Server and write an aspx web form or even better MVC framework.

I've split the database so that as many users as needed can use it without any problems.