I have several MapPoint "Export to Excel" type functions now in VB6 that I run in debug mode. The exports take a ridiculously long time, 3-4 hours for 16,000 records. My theory is that if I plop the code in Excel that has to be open anyway, I could eliminate the VB process and possibly speed things up. I am curious to hear others experience with this. Is it faster? The code transition is easy enough but I don't want to go through the trouble if it isn't faster.

Thanks

Are you using the MapPoint Control OCX?

I have found that if you write the VB6 code as a MapPoint Addin it generally runs 30 to 40 times faster.

Roger

I agree with the above comment. Here is a quote from the help file that supports the claim..

COM add-ins run in-process with MapPoint, so they generally run faster than COM applications do as stand-alone executables

I just wanted to update this post with what I have learned. I turned my Mappoint utility VB6 project into an MP add-in and it's true, it is way faster. To the tune of 80% faster. It was well worth the effort. However, running it in debug mode slows it way down albeit not as slow as before.

Thanks for the input.