Hopefully you're going to take some good advice and redesign the way you
store images. Images should be put into the file system which is where files
belong. The database is used to store data. Like data such as a pathname or
URL to where images are located. That is the best practice of web
development since Day One.
Why? I don't really know but I surmise perhaps because designers can be
taught to use FTP allowing them to put images into the file system on the
server when they need on demand access to images to create or edit content.
Otherwise how do they get their images? I wouldn't let some push button
monkey code "designer" touch my database. Would you?
Either way, you should build a stored procedure and pass arguments through
its parameters which will return data to the calling code which is used to
dynamically populate controls with properties. You can get a head start by
reading and studying the stored procedures that SQL Servers itself creates.
This is especially helpful if you're using 2.0 Membership. And of course
there are many blogs and tutorials that I've found helpful to help me learn.
<%= Clinton Gallagher
NET csgallagher AT metromilwaukee.com
URL
http://clintongallagher.metromilwaukee.com/
MAP 43°2'17"N 88°2'37"W : 43°2'17"N 88°2'37"W
