Client and server computers may have one or more security-based software (anti-virus, anti-malware, anti-spyware) utilities installed.
Common to security programs is the ability to define "exceptions" for program files and folders where scans should be ignored.
Including R:BASE within the exception area is required in order to maintain high performance. If R:BASE itself is scanned each time it is launched, and the contents of the database and temporary files are halted and scanned each time they are created/accessed, users will see much slower response times when running R:BASE, making connections, and accessing files.
It is important to add exceptions to three areas of the R:BASE program:
Program Executable
For R:BASE 11, the executable name is RBG11.exe. The default installation folder is "C:\RBTI\RBG11".
For R:Compiler/Runtime for R:BASE applications, the compiled executable, Runtime executable, and DLLs (all of which are usually stored onto the shared network location) must be defined as exceptions.
Database Files
For R:BASE 11, the database files are the .RX1, .RX2, .RX3, and .RX4 files.
Although wildcard may be accepted, adding each file extension individually as an exception may be more appropriate.
Temporary Scratch Files
When R:BASE is launched, it will create three .$$$ temporary files. After performing certain actions, additional files may be created, and the existing files will increase and decrease in size. Add the *.$$$ files as an exception.
It is also recommended to scrutinize the security product, specifically how it handles exceptions!
Some security products treat exceptions differently, where scans (manual and scheduled) apply for "folder" exceptions, however real-time (application control) applies specifically to "file" exceptions.
The above could mean that all folder exceptions applied in a security product do not prevent the R:BASE executable from being scanned when launched, nor do the exceptions prevent the database files from being scanned while accessed!
