Hello,
I'm a programmer myself and I must say that initially I also had some trouble with Avast. But everything is running smoothly now, after some config in Avast.
Especially Visual Studio + Avast gave us some headaches
Mostly because Avast proactively kept scanning (and sometimes blocking & vaulting) the newly compiled files when building the solution or debug-running them, which basically prevented me from testing and executing my assemblies/solutions. Plus, it sometimes totally messed up the solution as a whole, because important files went missing (moved to the vault).
I also had some issues with VBA in Excel, but we do not code VBA in Access (we only use MSSQL Server for DB projects). So, unfortunately I can't comment on that. Although the symptoms are likely similar.
Anyway, all issues, including those with Excel macro enabled files (VBA), were basically solved by adding the appropriate
files/folders to exceptions in Avast. For VS that mostly meant the Build and Publish folders (or the Project folder as a whole, but I thought that to not be the safest solution). I did
not add any
Blocked & Allowed Apps. I only used File/folder Exceptions: go to
Menu >
Settings >
General >
Exceptions > add files/folders there as required.
I hope this helps?
I must admit, though, that I am not sure if adding macro enabled MS Office files and executables, even trusted ones, to exceptions in Avast is practical and/or even wise. They can also still become infected after all! Are there any "best practices" documents or other advisories available from Avast for situations like these? That would probably help a lot of people, including the OP?