I have noticed that Citadel 5 database files are cached to the local client that is using those files for hypertrends and other historical data within Lookout. Is this by design, is there a way around this? This is terribly inefficient, considering databases can grow quickly to multiple gigabytes in size, and if a user has not run Lookout or other Citadel data applications (i.e. Measurement and Automation Explorer), it can take extremely long times for the data files to cache up to date. Also, I have found numerous security issues with regards to Windows XP and files caching properly from the server, and have yet to find an appropriate answer for how those files can consistently be cached.
I've been involved with multiple tech support requests on this and other issues with 6.0 as well as other discussions here regarding it as well. I think NI owes us as customers a decent explanation for what seems to be a poorly released software as well as an expected timeframe for resolutions on open issues. It is rediculous that a software with so many efficiency issues touted as a client/server application be released before major issues such as these are addressed.
