> I appreciate all the input. I would definitely like to use a separate table > for the zips, but I cannot figure out how make the form that stores them > user friendly.... each entry can have any number of zips - from many to just > a few. > > Also, the site is in development, so there is no existing data.... > > I will play with LIKE for the time being..... Aren't zip's fixed? Why do you need 'like'? What are you trying to achieve? -- Postgresql & php tutorials http://www.designmagick.com/ zips are fixed, but my clients have districts that I want to be searched by zip+4. Each client will have a different district with different zips per district. They are to input the zips that are within their district when they sign up, and that data is used to display relevant profiles when a user inputs their zip. As best as I can figure, the best way to do this with full text db fields where the zips are inputted separated by comas. I am currently trying to get WHERE MATCH () AGAINST to do the trick, but I am going to play with some of these other suggestions.... I am very new to programming, just fyi. Any input or suggestions very much welcome. Thanks, Don -- PHP General Mailing List (http://www.php.net/) To unsubscribe, visit: http://www.php.net/unsub.php
