[AccessD] Design Problem

I agree with Kath

(who described my preferred solution much better than I did :-O)

Chris Foote

> -----Original Message-----
> From: Kath Pelletti [mailto:KP at sdsonline.net]
> Sent: Monday, November 22, 2004 11:41 AM
> To: Access Developers discussion and problem solving
> Subject: Re: [AccessD] Design Problem
> 
> 
> Richard - I think if it was me I would only have one client 
> table, from what you have said, but with 3 separate fields there, eg.
> 
> 'Job' table:
> Job ID (autonumber)
> RequestorID (related to Client ID in Client table)
> PrincipalClientID (related to Client ID in Client table)
> RecipientID (related to Client ID in Client table)
> 
> 'Client' table
> Client ID (autonumber)
> Name details
> Address details
> 
> 
> The fields RequestorID, PrincipalClientID and RecipientID 
> would all relate to one Client table.
> 
> That way all 'client' data would be stored in the one table 
> and never duplicated, and you would have the flexibility of 
> having any combination of the 3 fields in the Job table. The 
> only mandatory field (it appears) would be the RequestorID.
> 
> HTH
> 
> Kath