Tford,
I know the coordinates from a zipcode table here in the Netherlands.
The user who has logged in has a zip code. Then he starts a query to find some sportclubs (like soccesclubs, hockeyclubs a.s.o.). Those sportclubs have zipcodes to. Every sportclub can do this.
That means (in theory) that 7000 sportclubs in the Netherlands can run the query. If I have to store the distance in a table, that means 7000x7000 (49.000.000) records in the table. Of course this will be a little less, but I still do think that working this way is not correct because it can be done lot easier (in other webapps, just calculate it runtime).
So, i want to calculate the distance with a calculated query field.