Jump to content

Unexpected Behavior with Vista and Write Protected Files


RobWright

Recommended Posts

I've noticed a bizarre behavior with LabVIEW running on Vista, and am wondering if this is a bug I should report, or if someone has already resolved this issue. This behavior occurs with both LV8.5.1 and 8.6.1.

Here's how to duplicate my issue:

1) place a path control on a front panel

2) click the browse button and navigate to a write-protected file

3) select the write-protected file, and then click OK

For me, doing the above actions causes a dialog box to be displayed that says something to the effect "You have selected a write protected file. Please select a different file" (or something very similar). It happens whether the VI is running or just in edit mode.

This is without trying to even read the file, just selecting it. Has anyone noticed this behavior? Is it Vista? Is it LabVIEW? Is it the interaction between them?

This issue precludes me from reading in the contents of any read-only file. Bizzarre.

Any help would be appreciated. Do you have the same issue? Does reading a write-protected file work OK for you?

Thanks very much, in advance, Rob.

Link to comment

This usually happens if you have the "New" or "New or existing" checked in the "Selection Mode" of the browse options and try to access a read-only, existing file. Try changing it to "Existing".

I've always thought that "New or exisitng" shouldn't behave this way. But just got on and worked around it.

Link to comment

Join the conversation

You can post now and register later. If you have an account, sign in now to post with your account.

Guest
Reply to this topic...

×   Pasted as rich text.   Paste as plain text instead

  Only 75 emoji are allowed.

×   Your link has been automatically embedded.   Display as a link instead

×   Your previous content has been restored.   Clear editor

×   You cannot paste images directly. Upload or insert images from URL.

×
×
  • Create New...

Important Information

By using this site, you agree to our Terms of Use.