LabVIEW and write protected DLL files

[Sunny]

Hi,

We are building Labview dll's within a source controled environment (ClearCase). These dll's can only be modified in a particular view, but they should be useable in other views. The problem is that LabVIEW seems to be unable to open and run a write protected dll. I don't want to do any unreserved checkout, i want to use automatically the latest version of these DLL's, but they are always write protected.

Does anyone runs in the same poblem and solved it?

Regards,
Sunny

[ThSa]

Hi,

it's not correct, that LabVIEW is unable to work with write protected DLLs!
So, please reword your questions more detailed!

regards,
Thomas Sandrisser

[Sunny]

Hi,

We use German Version of LabVIEW 6.1 and there is displayed an error message "Zugriff verweigert" in case of loading any VI referencing a DLL with Checked In state (we use ClearCase).
I made a copy of one of these dll files and set the write protection flag manually, the error message isn't generated (as you described). So it seems to a problem in interworking between LabVIEW and ClearCase!
We are working with ClearCase Dynamic Views and MVFS (Multi Version File System).

Any help will be appreciated!

Regards,
Sunny

[ThSa]

Hi,

i don't know something about the 3rd p. software sorry!
perhaps it's an option for you, to program an application, which copy the dll file into a new folder with "normal" attributes!

regards,
Thomas

[PFD]

Hello,

I know that the last message was post a long time ago, but I would be interested by a reply also, because I necountered exactly the same problem with Labwindows CVI 8.0 and clearcase 6.0. I mean :

My executable calls some DLL.

the DLL are managed by clearcase and not checkedout.

I have an error launching the executable.

If I just copy/paste the source folder from clearcase to a temp directory, then CVI executes normaly the project. It is the same behavior if I checkout all dll called by the executable.

I thought that calling a dll requires only read access!!!

Is anybody can help me?

Regards,

PFD

[Ecleamus]

Hi PFD,

You are correct that the dll need only to be read-only.  Unfortunately this alludes to ClearCase being the culprit. I would try the previously posted suggestion of programmatically copying the files.

Have a great day,

Ecleamus R.