[AccessD] Accomodation Register - Was: On DB Bloat...

Andy's interpretation of my comments is correct.  Here is an example:

tblPhotos		tblProperties
pkPhotoID_________fkPhotoID
PhotoPath		pkPropertyID
PhotoDate		etc.
PhotoComments	etc.

Or

tblPhotos		tblPropertyPhotos
pkPhotoID_________fkPhotoID			tblProperties
PhotoPath		fkPropertyID____________pkPropertyID
PhotoDate		etc.				etc.
PhotoComments	etc.				etc.



Mark


-----Original Message-----
From: Andy Lacey [mailto:andy at minstersystems.co.uk] 
Sent: Thursday, May 27, 2004 2:47 AM
To: 'Access Developers discussion and problem solving'
Subject: RE: [AccessD] Accomodation Register - Was: On DB Bloat...


I may be wrong Sturat but I think what Mark is suggesting is that you don't
make any differentiation on the Photo table between property and
Accomodation Unit photos, you put an FK on the property and Accomodation
Unit tables pointing to the Photo Id. Or, assuming you need >1 photo for any
unit, have a relationship table.

-- Andy Lacey
http://www.minstersystems.co.uk 

> -----Original Message-----
> From: accessd-bounces at databaseadvisors.com 
> [mailto:accessd-bounces at databaseadvisors.com] On Behalf Of 
> Stuart McLachlan
> Sent: 27 May 2004 00:00
> To: Access Developers discussion and problemsolving
> Subject: Re: [AccessD] Accomodation Register - Was: On DB Bloat...
> 
> 
> 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.
> 
> 
> 
> -- 
> _______________________________________________
> AccessD mailing list
> AccessD at databaseadvisors.com 
> http://databaseadvisors.com/mailman/listinfo/a> ccessd
> Website: 
> http://www.databaseadvisors.com
> 
> 

-- 
_______________________________________________
AccessD mailing list
AccessD at databaseadvisors.com
http://databaseadvisors.com/mailman/listinfo/accessd
Website: http://www.databaseadvisors.com