1. Can anyone explain the risks of using network locations for QSW files? I see that a "network fix" tool is available, but what does it do?
2. Why does Intuit use a local file location when file sharing and centralized backup are so important?
The only risks are that it's a PITA to maintain.
Just make sure each user using statement writer has network rights to the folder where the statement writer files are (I have a mapped drive for the users and that mapped drive is what I reference under preferences). I also had to login to each user's machine as a network admin and run the fix tool in order for the .Net assemlies to get granted to proper permissions. Just make sure the 2 batch files are actually on the desktop and not shortcuts. It seems that the last update to statement writer erased these settings and they had to be redone on each desktop using statement writer.
1. The risks are the additional maintenance required to support this configuration. The "network fix" tool simply grants some rights to the custom .Net assemblies that the statement writer uses.
2. I can't speak for that. My data file and reports are on a network folder shared with the users who need access and backed up twice a week.
