Hi Giles, I'd prefer storing a link in the db instead of the image itself. After 20 seconds of thought, here's a half-baked plan ... ;-) How about: (1) setting up an 'upload' directory for the client to load the pictures into. (2) running a scheduled job to move the pictures to the directory they should be in, check for duplicate names - overwrite or append a numeric - your choice, and add the link to the db. (Or give the client an "admin" page to run this process.) (3) the process would also clear out the 'upload' directory. (4) you could send the customer an email at this point ... or not. (5) have a password protected dynamic "admin" page that looks for pictures in the db with no <information about them> and lets the client 'fill in' the missing information for these new pictures and loads that into the db. HTH, RonL. -----Original Message----- From: Giles Carey | Element Design Problem: Client wants to upload own images to de siplayed from a db with information about them.