GS wrote:
madscijr wrote:
My question is, does anyone have any suggestions or know of any
utilities or ways to narrow down what is setting off the alerts?


You are not the first one.

Try renaming some of procedures/variables, moving code to
different
modules...
or
switch antivirus.

VBA code stored in bin file "looks similar" to virus.

You can start removing module by module and see when it stops
being
infected and focus in rearranging code in these modules.

FWIW:
I had my licensing code 'flagged' as a false positive suddenly, on
a
system that it ran fine on, after Avast did an update/upgrade. How
I
fixed it was to change wording used...

encrypt, encode
and
decrypt, decode

were changed to...

convert
and
revert

..after which the flagging stopped!



I had to rename procedure which originally was named kkk :)

No surprise! I learned that the av apps use binary combos of suspect
characters to evaluate. These, of course, are based on typical wording
used when programming malware!

--
Garry

Free usenet access at http://www.eternal-september.org
Classic VB Users Regroup!
comp.lang.basic.visual.misc
microsoft.public.vb.general.discussion