Now I'm back from lunch I shall elaborate
Brief bit of OO theory: You want to keep your member data private, it is easier to debug as there are limited ways to edit data and it is easier to enforce behaviour. So you need a public way to access the data
As I am sure you are aware, a useful part of non re-entrant VIs is that if they are called from multiple points at the same time, they must wait until the VI is availavble again, enforcing data protection and race conditions, etc... So if we use this as our member data storage
If you have multiple instances of an object, then you will need to implement a handler class which stores the children. e.g. you have a class called 'book' each 'book' object will store its own private member data. another class 'shelf' will store references to each book (usually in the form of an array) then you add to or remove from this array
Attached is a simple object class which should help. Pipe up if you're not sure on anything
_____________________________
- Cheers, Ed