without seeing us-zipcodes, i am under the impression that it only includes the lat/lon and does not provide any sort of calculations, which zipdyacs does. if this is the case, then zipdyacs should be modified to use the data in that table instead of keeping it's own lat/lon info.
also, zip codes can be stored as integers since there is no difference between the zip code 00872 and 872. It's not The Best way to store them from a textbook perspective, but from a practical perspective in regards to space and indexes it does work. Moot point if the us-zipcodes data is used.
james
