I have identified a conflict between NOD32 AV Business Edition 3.0.684 and Simply Accounting 2009. The situation is a Simply Accounting client machine connecting across an internal network using Simply's native connection manager to a shared network folder on a server. Connectivity is fine for the most part, and a user can work with the files with no problems UNTIL the user backs up the simply files, in this case to the local desktop on the client machine. After the backup successfully(!) completes (yes the backup itself is ALWAYS successful), Simply cannot re-open the database, crashes and reports an error. After this initial failure, connectivity is unpredictable, opening the database sometimes is successful, and sometimes fails. Only until the below solution is performed does it once again become reliable. The solution, such as it is, is to completely disable Scan on File Creation in the advanced settings for Real Time file protection system protection settings on the NOD32 install residing on the server. Strangely, once the above is done, and Simply is opened again on the client machine, (it is always successful once the above is done), if you then turn the Scan on File Creation feature back on in NOD, subsequent attempts to connect with Simply are successful, UNTIL the user tries to backup again! Stranger still, throughout all of this, at any point, I can navigate to the shared network drive to the Simply database files, and perform a copy paste to any local machine, indicating to me the files are NOT locked! Something about the unique way Simply is creating/modifying the files is triggering NOD to do SOMETHING to block it afterwards... Can anyone offer an opinion on this, pretty please?