MS Access vs MySQL

You are incorrect. A binary file is a binary file, and Access should store
jpeg, gif, pdf, or anything else you put into a binary field. The problem
is making sure it's read correctly when it's pulled out. Since I never
store files and only store the file paths in my database, I can't be of any
other help than to say you can certainly store what you want. It must be
some other problem.

"xcoldnet" <webforumsuser@macromedia.com> wrote in message
news:cvl1cp$31k$1@forums.macromedia.com...

> I am using MS Access 2002. One of the field of my table in the database

require

> to store images. I am realizing, please correct me if I am wrong, that I

can

> use only .btm or .psd (photoshop) files as the sources for the images.
> Basically if I pass a .jpg or .gif image I am going to get an error, as it
> happens using <CFINSERT> at the moment. So the question is: Will MySQL a
> better choice than MS Acess 2002 in order to store and retreive images

like

> .jpg and .gif? Thank you, Dario
>

sorry, not an answer just to ask, why do you store the images in the DB?
I think the best approach is to store just the file names in the DB
& the images in a folder

manuel

xcoldnet wrote:

> I am using MS Access 2002. One of the field of my table in the database require
> to store images. I am realizing, please correct me if I am wrong, that I can
> use only .btm or .psd (photoshop) files as the sources for the images.
> Basically if I pass a .jpg or .gif image I am going to get an error, as it
> happens using <CFINSERT> at the moment. So the question is: Will MySQL a
> better choice than MS Acess 2002 in order to store and retreive images like
> .jpg and .gif? Thank you, Dario
>