Then it seems that you would just need the state, county and zip relationship to manage adding of zip codes and then associate the zip codes to a coordinator via the bridge table.
tblState - stateID tblCounty - countyID - stateID tblZip - zipID - countyID Then associate it to a coordinator. tblCoordinator - coordinatorID tblZipCoordinator - zipID - coordinatorID So your application would manage add/update/delete zip codes, add/update/delete coordinators and then linking them together on the tblZipCoordinator. Teddy On 8/25/06, Richard Dillman <[EMAIL PROTECTED]> wrote: > > All the contacts will be inside Indiana, USA so lets say Marion County > will > be split evenly between to people by a list of zipcodes where > the zipcode > range is in Indiana so 46001 - 48000 > but sence they are in Marion County the list is 46107 - 46298 > > I definately see where a cCounty Coordinator will be county wide but a > Training Coordinator could be at the city level so based on zipcode but > not > in every county. > > Does that help clear it up any? > > -- > Richard Dillman > [EMAIL PROTECTED] > (317) 916-8341 > > "I think it's T double-E double-R double-R double-I double-F double-I > double-C, C, C." - the Goose in 'Charlotte's Web' > > > ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~| 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-Talk/message.cfm/messageid:251087 Subscription: http://www.houseoffusion.com/groups/CF-Talk/subscribe.cfm Unsubscribe: http://www.houseoffusion.com/cf_lists/unsubscribe.cfm?user=89.70.4
