My company uses a spreadsheet with an embedded map, and a few users are completely unable to export data from the map to an excel sheet.

The users have identical hardware setups, most of which being brand new Dell D820s.

here is a screen cap of the error I receive:



Clicking Switch To... just reproduces the error window, as does Retry. Cancel just produces an error that tells me that the data cannot be exported, and to check whether or not Excel 97 or later is installed, which is not in question.

Anyone have any experience with this?



***edit***

Sorry, forgot to mention, this is using MapPoint 2004.

Hi,

It is possible that your program that uses mappoint is not pumping messages. Then you get that window if it uses a COM object.

Another possibility is that you did not return soon inough from out of a mappoint event (even if you are pumping). I think the timeout is 10 seconds.

Another possibility is that if you use the ActiveX that there is mappoint instance already in memory from a previous instance that is not properly destroyed.

I think all reasons of this message are covered as far as I know.

Another reason for this message is interactive debugging. The debugger sets a breakpoint which prevents the message loops from executing.

In Excel, debugging may be automatically engaged if there is an unhandled error in the VBA code.

HTH
Paul

Hi Paul,

Thanks for completing this. I forgot the debugging (I dont write bugs hehehe).

In Excel, debugging may be automatically engaged if there is an unhandled error in the VBA code

Do you mean that the debuger is invoked automatically with an unhandled error ? So this means that it is possible that this message window is because an unhandled error. Did I understeand that right ? But then Excel will stop and show the execution point, or not ?

Yes - it will stop and prompt to debug the code. Since mappoint is still executing out-of-process, the error gets compounded.