Jon Sjöstedt

Hello all! In order to not jeopardize concurrent access to a file, I have made some tests with the "deny mode" wire to the "open file" vi. It seems to work (I am using lv 7.1.1 on Solaris). I do accesses from different hosts that map the same NFS partitions. Looking at the file properties during execution of the tests, no permissions are altered. Neither can I see that any kind of lock file is created. I have also noticed the the file is only locked for labview. I can access the file perfectly with emacs or cat. My question is therefore: How is this "deny mode" functionality implemented in solaris? I dont want to break it unintentionally.

visaconf gave this funny dump (attached). I will ask admin to redo install with this new information. Thanks.

I hve tried reinstall (that is, the administrator has reinstalled it for me). That did not help. I keep getting "Error -1073807202". Any ideas?

The dqGOOP installer did not work on my windows machine (note: I run lv remote on a linux machine). Can the dqGOOP framework be fetched in a more general format? dataact.com didn't answer my mail... Edit: Got my hands on dqGOOP-core

Guess this was unclear QUOTE Clarification attempt: I am not looking for OOP design elements in general. I am specifically interested in a way to access data in pointer-style (=refnum?). Dataprotection is desireable if possible. I have noted the very elegant LV2-style singleton design (which uses no magic *OOP-package or LVOOP) and need to complete it with a non-singleton datastorage. Hope this was more clarifying than confusing... I will look into dqGOOP and see if that gets me where i want. Thanks for all help so far!

Sorry for my late reply. Vacation... normandinf: There is some "political" resistance within my organization against OOP in general, caused by improper use in previous projects. I'm also impressed by those *OOP-packages that allowes access to data using ref's and would like to know if there is an easily reuseable method behind it. By experience I guess that the newly introduced (lv8.2) OOP-constructs are not that reliable (I am unfortenately stuck with lv8.2) until a few versions later.

Hello all! First post. I wrote a long nice message and then IE crached. Im looking for design patterns for encapsulation and protection of data. Very much like an object with private data (but not a singleton). I would like to accomplish this by not using LVOOP. Data/object should be referenced by a refnum (I imagine). Guess there is a default solution to this that I dont know of. All ideas welcome!