[!--quoteo(post=357562:date=Mar 23 2006, 07:24 AM:name=lpxxfaintxx)--][div class=\'quotetop\']QUOTE(lpxxfaintxx @ Mar 23 2006, 07:24 AM) [snapback]357562[/snapback][/div][div class=\'quotemain\'][!--quotec--] Why would you store imges in the db? Why not just store the image's information in the db? I'll let you look at my source for uploading images. I've successfully uploaded more than 2 MB. P.S. Are you from BWH? [/quote] Well, I tried to show my code, but the site didn't like that. I couldn't use the code tag properly, so yeah... Everything is stored in the database to bypass permission problems that we can't manipulate on the school's server. Initially, we just had a "reference" field that would hold the relative path to the image file, but we couldn't get the image on the server. So, we decided to put it in a mediumblob in case it went over the 64K. 16MB seems safe enough, and we were told disk size isn't a concern... We're building a CMS that's used when a local company wants their site updated. Unfortunately in the past, the group/class that built the site has graduated/moved on, and we all know how tough using another's source code can be. So, the CMS would, in theory, allow another group to make requested changes or even allow the end user to do the changes. I'm not sure what BWH is, so I'll go with 'no.'