I have an application built into an exe with LabVIEW 8.2. It uses 1 simple call to user32.dll to determine if caps lock is on. When I build the application, it copies user32.dll to the 'data' subdirectory of my application. Everything works fine, however when I exit the program it throws a Windows error, "... has encountered a problem and needs to close..." Now the fun part. If I remove user32.dll from this directory, everything works fine. I guess it just goes out and finds the original user32.dll in the system directory and there are no errors when I exit. Replacing the file in \data causes the error again. The simplest thing would be to remove the call in my program as it isn't absolutely necessary (it just shows a warning when entering a password if caps lock is on), but there seems to be something weird going on because it only throws the error when using the dll it copied. Is there any way to stop the application builder from copying dlls? I couldn't find anything. Is there a way to force LabVIEW to release and cleanup any dlls it is using? If I could do this when the user exits, maybe whatever is causing this won't get left behind.

Some courses and learning paths on NI Learning Center may not appear on learner dashboards. Our team is actively investigating.

If you encounter access issues, please contact services@ni.com and include the learner’s name, email, service ID or EA number, and the list of required courses.

LabVIEW

User32.dll Causing Error on Application Exit

Author

Yes that clears up what you last said. Also I'd like to add that it works the same if you just put the name of the dll in the dialog box without the full path as someone suggested above. It won't be copied to the application directory this way either.

Thanks for your help.

Message 11 of 11

(576 Views)

LabVIEW

User32.dll Causing Error on Application Exit

Re: User32.dll Causing Error on Application Exit