Improve performance of Virus checker on Candy Data

Introduction

Candy opens and closes its files continuously. In a multi-user environment this occurs for almost every data record access. If an anti-virus program is scanning these files then Candy will slow down considerably.

If the virus checker holds up a read or write process for too long then Candy will crash because ‘the file is in use by another process’.

Candy data files are proprietary. No virus can infect a Candy file without corrupting the file. Candy will not recognise executable code inside one of its data or text files. Candy has no data macro system that can be infected. For this reason, scanning Candy data files is not lowering the threat level on a computer.   

SOLUTION 1 – improve performance quickly

Change your virus checker to only ‘scan on write’ instead of scan on read and write.

SOLUTION 2 – exclude data folder

Exclude the entire CCSDATA folder from being scanned ie C:\Users\THISUSER.DOMAIN\Documents\CCSDATA or F:\THISUSER

Also exclude the MY CCS folder which is found in the user profile MY DOCUMENTs ie: C:\Users\THISUSER.DOMAIN\Documents\MY CCS

SOLUTION 3  - exclude specific extensions

Candy file extensions do not denote the file type but rather the job that they belong to. This means that there is not one extension that can be excluded ie A01, B22, C99...
If the virus checker allows wild cards to be used in the exclusion list then the following would be true:

Static extensions

.LOC
.4PF

Network data extensions

.Z?? [network master]
.S?? [multi user company]

Normal data extensions

.A??
.
B??
.
C??
.
D??
.
E??
.
F??
.
G??
.
H??
.
I??
.
J??
.
K??
.
L??  
.M??
.
N??
.O??
.
P??
.
Q??
.
R??
.
T??
.
U??
.
V??
.
X??
.
Y??