>>> It did get the exchange on the correct side of the road,
Thats probably more down to luck
Problem is a postcode can cover a particular area.. so it plumps for the middle bit.
I have done the calculation bit a bit differently than some other sites and afaik its the only checker that is supposed to give road distance as elsewhere quotes "crow flies".
Ive seen crow flies quoted so many times that I thought it would be a good idea to put road distance which is more likely to be true rather than the other measurement.
I must admit though that I did have help with that and chris did it for me as an include whilst I did the maps and conversions to get from long/lat and pass it through... But chris must get the credit for the actual road calculation bit.
Aside from that then the rest of it blame me if it goes wrong - as chris said nowt like jumping in at the deep end for a first proggie in a new language :/
Big Credit must also go to Sam too where the database files come from and Im using his API which keeps records of which LLU providers are at which exchanges etc. afaik other checkers use that too - they just dont make it obvious and give him the due credit.
Only thing that does bug me is sometimes acess to the BT d/base is a bit slow and it will sometimes take its time checking a phone no :/
- When it does that it sometimes produces an error code - but will still send the results back. I think it must depend on how busy it is.
It also takes its time if its a "non BT line"..