Bob, I think you're already on the right track of creating a mapping table that associates the propertyID and multiple imageID's. With a table, it gives a lot more flexibility to scale your app since you can begin storing various image attributes on the database including file exts, and size etc. You can also use it to store the orig file name (smith_home.jpg), so you can change the actual(physical) file's name to have your own assigned naming convesion like "img_123.jpg" where 123 is your propertyID.
> -----Original Message----- > From: Bob Imperial [mailto:[EMAIL PROTECTED] > Sent: Monday, July 31, 2006 10:21 AM > To: CF-Newbie > Subject: multiple image uploads > > 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:1940 Subscription: http://www.houseoffusion.com/lists.cfm/link=s:15 Unsubscribe: http://www.houseoffusion.com/cf_lists/unsubscribe.cfm?user=11502.10531.15
