eenauk

users of the application. sorry abt the confusion. we need to log any changes users make to the db and make sure they only have access to allowed features.

I am designing a rather large LIMS (Lab info mgmt sys) for a highly regulated company. we therefor need a high level of security and logging. This would seem like an ideal opportunity to try aspect-like programing in LV. I know that a full AOP in not reaaly possible in LV, but am wondering what suugestions y'all might have at the back of your heads. Here is mine at least (feel free to chop it to bits before i get all messed up in it): The basic idea is to create a "run-time aspect server" that will monitor (via vi server) all GUI opens and closes. - On opens, it would check to make sure the current logged-in user has rights to open that vi and would grey-out any features to which he or she should have no access, alternately aborting (?!) the vi (this should of course never happen). - On Closes, it would pop-up a (FDA-required) box for the user to describe any changes made, if the vi did actually perform any data changes (ie INSERT, UPDATE or DELETE statements - all data is stored in a dB). What i want to avoid is having to have all wireworkers on the project have to remember to include a special vi in both the init and close sequences of all their GUIs, but perhaps that is the 'best' solution after all. michael

hi - i am working on a sub-GUI (displays a tree control) that pops up from the click of a button on the main GUI. Each time it opens, the sub gui generates an occurrance, which it feeds into a sub-vi. This sub-vi continuoulsly runs a while loop containing an event structure that controls the tree. when the user clicks OK/Cancel in the sub-gui, this gui sets the occurrence so that the sub-vi stops and we return to the main GUI. My problem: the sub-GUI generates the same occurrence on each new run (unless you recompile it). Also, when the sub-GUI is opened a second time, the occurrence still seems to be set so that it stops immediately. Note that i cannot set the "Wait On occurrence" vi to "ignore previous" since it needs to time out every 50ms and would therefore not catch most of the occurrences at all. Q1: do you know how to generate new occurrences each time a vi runs? Q2: do you know how to "clear" an occurrence? thanks. michael. PS i've attached a simplified version of the vis, but the llb still contains 84 or so vis.

Thanks that is exactly what i was looking for! just for clarification: i have a large program that dynamically loads multiple modules. since these modules might have been compiled at different times with different versions of the same vis, conflicts could occur in LV's memory management. therefore i need to make sure that each vi that is loaded has a unique name. thanks again, michael

i need to come up with a plug-in architecture for a bunch of compiled instrument drivers and program modules. My problem is that these drivers/modules all use a bunch of 'shared code' which often changes. Therefore I need to make sure that none of the separate plug-in exe's have vis with the same name but different back pannels (otherwise vi server gets all mixed up). As far as i know, making dlls does _NOT_ fix the problem (ie they also require vi server). The only other solution i know of is to save all the vis for a given module/driver to their own llb, renaming them all with specific pre- /suffixes. I cannot find a way to do this programatically and really don't care to do it all manually for each vi. Suggestions? Michael