I'd go the separate table route with the image file name and the propID. However, I've done quite a few RE sites, and the system that I use only allows them to upload 10 images per listing. So, what I do is add 10 image fields (image1, image2, ..., image10) to the listings table. That's just me, if you think this thing is going to morph into something bigger, or you are going to allow arbitrary amounts of images, this approach obviously won't work for you.
Bob Imperial wrote: > Hi folks ... pondering how to approach adding multiple image uploads to > associate with an existing db entry. I have a little app I'm building for a > commercial real estate company to display property listings and their > pertinent info, I'm wondering about the logic behind doing multiple photos > uploads to tie into a single propertyID. My intial thought was to use a > simple text field to store the image name, but in my current thought > processes this only works for single image uploads. I was thinking about > possibly adding another table to store PropertyID along with imageID and > names that way but I fear I might be making this more complicated than it > needs to be .... any ideas would be greatly appreciated. > > Bob > > ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~| Introducing the Fusion Authority Quarterly Update. 80 pages of hard-hitting, up-to-date ColdFusion information by your peers, delivered to your door four times a year. http://www.fusionauthority.com/quarterly Archive: http://www.houseoffusion.com/groups/CF-Newbie/message.cfm/messageid:1938 Subscription: http://www.houseoffusion.com/lists.cfm/link=s:15 Unsubscribe: http://www.houseoffusion.com/cf_lists/unsubscribe.cfm?user=11502.10531.15
