If the problem you're having is that your application is crashing, but you can't debug it because you can't reproduce the crash in the computer where you have the CVI development environment installed, one strategy you should consider is to remote debug the application. To see whether this would be feasible, try building a debug version of your DLL or EXE and replace the one that you installed in the other machine with this one. Then see if the problem still happens. If it does, that means that you should be able to debug it.
If you haven't debugged remotely before, and you need to find out how to do it, launch the CVI help, then type "remote debugging" in the help index. That topic should explain everything. But do feel free to ask some more questions if something doesn't make sense.
A simpler, but more tedious alternative, would be to sprinkle some message popups throughout your application, close to where you suspect the crash is taking place. After a few iterations of doing this, you should be able to pinpoint exactly where it is crashing, and that might also tell you why it's crashing. You can do this either in a debug or release build.
Luis
