We currently distribute our global library over a network folder using hard coded Enviromental Veriables. The problem is that we have no way of knowing when the library was last updated. This can cause users to be un-aware of recent library updates or if they are using old revisions of the library (due to network issues or download problems). Does anyone else have this problem or found a solution?
In reply to jch teyssier: