Reverse Geocoding a Lot Slower in 2004 and 2006

Compared to MapPoint 2002, has anyone else noticed that reverse geocoding is a lot slower in MapPoint 2004/2006 ?

In general, what are some strategies for speeding up reverse geocoding, I need to do about 1,000 per hour.

Ideally I need to process at under half a second for each one. Is that a reasonable goal?

Thanks!
Eric

Related to this question, is there a commercial dll or solution for doing fast reverse geocoding with MapPoint 2006? I know there was a popular thread where someone claimed to have built one but then disappeared.
Eric

I found these two threads --
http://www.mapforums.com/slow-reverse-geocoding-5116.html
http://www.mapforums.com/reverse-geocoding-3544.html
I'll try Richard's suggestion on making sure objects are cleaned up, I suspect this may be it as the memory usage grows and grows! that would be a good indication :-)
Eric

Unfortunately memory usage grows regardless of how tidy you are. I think the garbage collector is lazy, and will tend to let the memory allocation gobble all memory that is available.

Restarting MapPoint or Wilfried's minimize/maximize trick is a good way of tidying things up. Microsoft should add a method to the API to force garbage collection.

Richard

The DLL mentioned was developed by me but there was a problem with people tying to connect to it as it was created in Delphi and this made connecting to it quite complex from some development environments.

I have now modified the code and created a small application that can be connected to via TCP and reverse geocode requests made to it, the application will reverse geocode approx 8 requests per second in either MP2004 or MP2006

If you would like to work with this application please message me or email me directly on "nigelafford at gmail.com" and I will happily send it to you.

Regards
Nigel