I have a vb6 app that uses the MapPoint control. I recently recompiled the app (after several Windows updates). Now, only on Windows 2003 servers, whenever I load the form in my app that contains the MP Control, I receive the vb msgbox with "Run-time error '16391'". I have tried re-compiling the app on an XP Pro machine, a 2000 Server and a Win 2K box. The app that was compiled on the win 2K does NOT exhibit the error when run on a Windows 2003 server. This would lead me to believe that something in the Windows update for XP and/or 2000 server has introduced some incompatibility. Has anyone else seen this behavior?

Hi,

Compiling on any machine should produce the same executable, so you have strange result. I did some search about that error but could not fount anything, tryed also the hexadecimal equivalent but also without result. You absolutely sure of the error number ? If it is a VB error I'm pretty sure it is documented somewere.

Turns out that the problem was version-related. I had MapPoint 2004 and MapPoint 2006 installed in my development environment. And even though my vb Project had all components and references pointing to the 2004 files (*.ocx etc.), the 2006 objects were being included in the compile. When running the app on a system running MP 2004, 2006 control references caused the run-time errors. I still do not understand why this will only happen when run on 2003 server. In any event, uninstalling MP 2006 from the development environment took care of the problem.