Heres a snapshot of the zip table where the data im using to test is located, as well as a ss of the events table (i used print view since its a wide view).
What i dont get is using "33914" returns the search results as expected. Using "35004" returns nothing. Yet theres no reason that it should not. I tried re-arranging where the row is located in the zip DB and no difference. The search only goes by zipcode, lat, and lng so nothing else should matter. I dont get why the code works for one and not the other. I even deleted the "33914" entry from the events table and it still did not return the "35004" result.
The "zip" table uses "zipcode" as the primary key. The event table does not have a primary, as there may be multiple entries for each zip and/or club so i really cant define a primary.
Note that the lat/lng rounds when entered into the evnts table. BUT this doesnt seem to affect the 33914 return so why would it affect the other? In the zips table lat/lng are set varchar(20) and in the events table they are float(10,6). Perhaps i should drop the float setting on the events table and do them the same. I'm not geocoding based off either table im using fetch for that so float really isnt needed.
