The error description always has a long path through numerous VI's that make up the application builder package pointing to where the error occurred. But the description never seems to give any detail about what actually caused the error. It is often too long of a file name, or too deep of a path that gave too long of a path/filename which the app. builder VI's could not handle.
It would be helpful to both the people who are having the issue, and to the people trying to help on the forums when they post their message asking for help, to have some information as to where to look.
Maybe that information is already available and I just don't know where to find it. Fortunately for me, I don't think I've come across this problem. One, I haven't need to build a whole lot of executables. Two, I keep my project folders at the root level of my hard drive, so the initial part of the path is always short. (e.g. c:\ProjectFolder\......) I know if you stored projects in a My Documents directory, the initial path is ridiculously long because of the way Windows locates My Documents on your hard drive (e.g. C:\Documents and Settings\My UserName\My Documents\ProjectFolder in XP) so you've already wasted 40-50 characters even before you give the directory name for you project folder.
My request: Let's show some meaningful information in the error dialog box for Applicaiton Builder errors that can help people figure out how to fix it.