Hi condor31,
The only thing which is concurrent is the license file. The DIAdem installation is still local on the client computer, which means that client A's DIAdem is completely separate from client B's DIAdem, because the two DIAdems are running on completely different computers. So you don't have to worry about collisions at the REPORT object level at all. If DIAdem A and DIAdem B attempt to access or update the same external files (layout files, data files, etc.), then the usual file access rules apply. Both DIAdem A and DIAdem B can load the same layout or data file from computer C, say, and play with them back on computers A and B, respectively. If DIAdem A then overwrites the layout or data file on computer C with an updated version, DIAdem B doesn't notice, because DIAdem B has those files in memory on computer B. If DIAdem B subsequently overwrites the layout or data file on computer C, then DIAdem B wins and its version of the file is now on computer C, though DIAdem A doesn't know this has happened. If you want to protect a particular data or layout file, you can of course set its Windows read-write permissions to read-only, then neither DIAdem A nor DIAdem B will be able to change it, though they will be able to read it and use it and save the edited version to a new data or layout file.
The one exception to this is if DIAdem A and DIAdem B happen to register-load the same data file, then they each have an implicit link back to the data file on computer C, and neither will be able to change that data file, since register-loading opens the data file read-only and puts a lock on it so that no one can change it while you have it open, but this is a special case.
Brad Turpin
DIAdem Product Support Engineer
National Instruments
