The issue is testing to see whether particular AV software issues false positives.Originally Posted by XL-Dennis
In my own code, I've seen false positives merely because I used a WordBasic.Kill statement. Of course, I can avoid that.
But I've also seen false positives due to late binding or use of the VBIDE at run time. Sometimes I have to use one, or both, of these mechanisms.
I could avoid late binding by having a different version of the code for each Word version, but that should be unnecessary.
My concern is that I use only NAV because that is the most common, but lots of folkes use other AV software.
I only use the latest version of NAV on one OS on each multiboot system, so I guess I could replace the earlier version of NAV on another OS with, say, McCaffee, but that would be with a different version of Office than on my latest system.
McCaffee is often available for $0 AFTER rebates, so I'll likely do this next tyme I see such an offer.