Microsoft Visual C++ Runtime Library...ERROR!!!!!!

[PCDMISRON]

Good day, All!!! Has anyone here ever experienced the following error message?

Microsoft Visual C++ Runtime Library
Runtime Error!

Program: C:\Program Files\WAI\PC-DMIS V41\pcdlrn.exe

This application has requested the Runtime to terminate it in an unusual way.
Please contact the application's support team for more information.

The message pooped...er, um...popped up when a colleague was attempting load a program which had been written at an offline workstation onto another offline workstation as well at the CMM.

I have experienced these Runtime errors when attempting to import programs particularly MMiv programs into PC-Dmis, but this program was written in native PC-DMIS. I have previously disclosed this to the tech support at Hexagon and have not really received any definitive feedback as to why this is happening and what can be done to minimize and/or prevent future possibly untimely recurrences.

I genuinely appreciate any and all input anyone who has prior knowledge of this can and would share.

Thanks,
Ron

[craiger_ny]

Runtime is usually source code math that can not be done to put it in simple terms but the more complex the software then the more complex the source of the problem. A simple example would be anything divided by zero, that will return a Runtime error but there are many other scenarios all related to the .exe's source code that will return such an error. Probably not going to get much hep here.

[PCDMISRON]

Problem Resolved...Sort of...

Runtime is usually source code math that can not be done to put it in simple terms but the more complex the software then the more complex the source of the problem. A simple example would be anything divided by zero, that will return a Runtime error but there are many other scenarios all related to the .exe's source code that will return such an error. Probably not going to get much hep here.

Thanks, Craig and you are exactly right in your analysis...After some additional screwing around loading probe paths, it became evident that there was a problem retrieving relavent file information from the server and after going to th local files on the machine, the problem was resolved.

The scenario was exactly as your anology of dividing by zero. The software was looking for something that was not there at the time, thus the error.

Thanks again...it is great to know that there are people like you here with vast reservoirs of knowledge regarding the PCD software and compooters in general...lol...the surface of which I have only begun to scratch.

Ron