Unlock file and folder attribute does not work in LV 2012

[PragmaTest]

Hello,

It is 2012 11 december, I use LV 2012 f3, and the problem has not been solved...

WTF !

[PragmaTest]

No answer...

NI, where are you ?

Are you lost ?

[Norbert_B]

Callahan,

you should read the posts carefully:

The development team is working on this and the next update may have already solved this problem.'

This sentence shows that NI is not promising that the next release (which would be 2012SP1) will (with 100% chance) include the fix. But it does likely include the fix.

2012 SP1 is not released yet, so please be patient. I am sorry, that no earlier solution can be provided (nor garantueed).

Norbert

[PragmaTest]

But imagine, it's totally impossible with a LV 2012 application to write in a file located in C:Program Files

!!!

How can I explain that to my customer ?

It's not a little bug, it's a huge BUG

[billko]

---

@Callahan wrote:

But imagine, it's totally impossible with a LV 2012 application to write in a file located in C:Program Files

!!!

How can I explain that to my customer ?

It's not a little bug, it's a huge BUG

---

IMHO, you shouldn't be writing (data) files there anyway.  There should be a dedicated folder for it.  What happens if you uninstall the app and it deletes those files?

In the old days, it was common to write to the program files directory.  Nowadays, you see data being saved mostly to a folder in the "My Documents" folder by default, or a folder in "My Apps" if it is config data.

[PragmaTest]

I'm not agree.

It's really common that an application write in its .ini configuration file at exit.

[billko]

---

@Callahan wrote:

I'm not agree.

It's really common that an application write in its .ini configuration file at exit.

---

Not so on my computer, at least.  I looked through all the program folders in my "program files" directory and I was hard-pressed to find any files that were modified since installation (but in all fairness, that doesn't mean something new would be written if I changed an option).  I found that what used to be in .ini files in the "program files/thisapplication" folder now reside as xml files in the MyApps folder.

But I know our experiences are different, and you are obviously not lying, and that's why it was just my opinion.

But why would you have to explain to your customer that you couldn't write to the program's folder?  If I were the customer, that would be the last place I would be looking for data... and it's really none of their business where you save your config files.  In fact, it's usually better NOT to tell them where they are, if you get my drift...  😉

[Bob_Preis]

You guys can track the progress of this problem with CAR 377164. I recommend giving it another try in 2012sp1. Also, in the meantime, if you unlock a folder, try changing the default install dir such that unlocked folders are not relative to the default install dir as a temporary workaround. I hope this helps. Thanks.

[didje007]

Hello,

First of all sorry to dig this old thread but I ran into this same problem.

How can I track the progress of CAR 377164. A search  on the Ni website doesn't return any meaningful results. (car means "because" in french which doesn't help)

Thanks

[ValkoA]

Hi Didje!

CAR, or Corrective Action Request is an internal tool to track various bugs and changes in LabVIEW, so it has no public availability. We do publish important CARs through the Known Issues page.

Regarding the problem in question, it has been fixed as of LabVIEW 2012 SP1.

Best Regards:

Andrew Valko

NI Hungary