Join 244,310 Programmers for FREE! Get instant access to thousands of experts, tutorials, code snippets, and more! There are 864 people online right now. Registration is fast and FREE... Join Now!
If you are using an Access database to store images, you should add an OLE Object field to the table, and store it there. the storage procedure is the same as it is for other record inserts.
Although your motivations are your own business, I would be remiss if I did not mention that physical storage of images to a database (especially Access) will lead to db bloat and application slowdowns in the long run.
In the table you want to store your movies, create a field that has LONGBLOB as the datatype. If you need further information on how to get the AVI in to mySQL, I would suggest looking at this article:
I too will say the same thing Amadeus said. Storing images or other binary data in a database is not the best idea. You will end up with database bloat and problems with your applications under load. It's much better to just store a reference to the file.
In the table you want to store your movies, create a field that has LONGBLOB as the datatype. If you need further information on how to get the AVI in to mySQL, I would suggest looking at this article:
I too will say the same thing Amadeus said. Storing images or other binary data in a database is not the best idea. You will end up with database bloat and problems with your applications under load. It's much better to just store a reference to the file.
Welcome to dream.in.code!!!
Iam using access i wnat to store images either in the database or on the server with a link in the database. I can insert the link for the image if uploaded to the server but it wont upload the image, or it uploads the image to the server but doesnt create a link in the database where am i going wrong please help me Jay Iam using coldfusion7 and access 2003..
It should be noted that in all "I want to store random binary stuff in my database" scenarios, it's generally not ideal. Sure, it sounds cool, but it's just not what databases do well and they tend to do it under protest. Consider long and hard why a filesystem solution is not preferred before traveling down this path.