File Dialog Crash

[robweaver]

Whenever I run my built application it crashes at the File Dialog (Express VI). Everything works fine in development mode and I've built this application many times in the past without ever seeing this problem. I've only seen it occur so far on Windows 7 PCs, but it doesn't occur on all Windows 7 PCs.

Built using LabVIEW 2010 and see the attachment for what the result looks like when it crashes.

Any help would be greatly appreciated,

Thanks.

[smercurio_fc]

That doesn't look like a crash as much as it looks like Windows is waiting for something. Could it be a network issue, in that you are trying to access a network path?

[robweaver]

The application isn't accessing any network paths.

[Thør]

What path is it looking at for the files?  The file dialog here is a Windows object that is told to open by LabVIEW.  It seems like Windows is having a hard time looking at whatever folder it's trying to browse in.

[robweaver]

I use this dialog in several locations. Sometimes it is called with an existing local path and sometimes (mostly on first calls) it is sent nothing (not wired), an empty path or not a path, which from the documentation I thought was supposed to default to the last path used by the file dialog:

start path

Path of the directory whose contents LabVIEW initially displays in the dialog box. If start path is valid, but does not refer to an existing directory, LabVIEW strips names from the end of the path until the path is a valid directory path or an empty path. If start path is invalid or unwired, the last directory viewed in a file dialog box initially appears in the dialog box.

Fom what I've been able to determine so far, it seems to hang like this on the occassions when it is not given a path or is given an empty or not a path.

What I'm still having trouble with is that it doesn't behave like this on all Windows 7 machines I've tested?

I guess the workaround will be to manually manage the previous paths for the different calls to the dialog to ensure that all dialogs are fed a relevant recent path (instead of just hardcoding paths for the dialogs, which wouldn't be very user friendly).