Stuart McLachlan
stuart at lexacorp.com.pg
Wed May 26 18:00:26 CDT 2004
On 26 May 2004 at 10:47, Mitsules, Mark S. (Newport Ne wrote: > If I understand correctly, you already have separate tables for Properties > and AccomodationUnits. Why not just have a separate table for photos? > > tblPhotos > PhotoID > PhotoPath > PhotoDate > PhotoComments > > PhotoID would be the FK in each of those tables. I think that would allow > the greatest flexibility. You could have photos of anything you track in > your db...staff, repairs, scanned documents, etc. > I do have a separate table or tables for photos. The question is how to differentiate between property and Accomodation Unit photos. Which of these is the best option (or is there a better one) 1. Two separate tables like your's one for Property photos, one for Accomodation unit photos 2. a single table with a Property/AccomUnit flag and a single FK that would link to either tblProperties, or tblAccomUnits depending on the state of the flag., or 3. a single table with both a Property FK and an AccomUnit FK (only one of which would be used) -- Lexacorp Ltd http://www.lexacorp.com.pg Information Technology Consultancy, Software Development,System Support.