Home |
Search |
Today's Posts |
#1
![]()
Posted to microsoft.public.excel.programming
|
|||
|
|||
![]()
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. |
#2
![]()
Posted to microsoft.public.excel.programming
|
|||
|
|||
![]()
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! -- Garry Free usenet access at http://www.eternal-september.org Classic VB Users Regroup! comp.lang.basic.visual.misc microsoft.public.vb.general.discussion |
#3
![]()
Posted to microsoft.public.excel.programming
|
|||
|
|||
![]()
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 :) |
#4
![]()
Posted to microsoft.public.excel.programming
|
|||
|
|||
![]()
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 |
#5
![]()
Posted to microsoft.public.excel.programming
|
|||
|
|||
![]()
These tools need to be able to explain exactly where the problem is. I'm sure it's a false positive but hunting down the issue(s) is a needle in a haystack...
On Friday, August 21, 2015 at 8:18:09 AM UTC-4, 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! -- Garry Free usenet access at http://www.eternal-september.org Classic VB Users Regroup! comp.lang.basic.visual.misc microsoft.public.vb.general.discussion |
#6
![]()
Posted to microsoft.public.excel.programming
|
|||
|
|||
![]()
These tools need to be able to explain exactly where the problem is.
I'm sure it's a false positive but hunting down the issue(s) is a needle in a haystack... Absolutely!!! -- Garry Free usenet access at http://www.eternal-september.org Classic VB Users Regroup! comp.lang.basic.visual.misc microsoft.public.vb.general.discussion |
#7
![]()
Posted to microsoft.public.excel.programming
|
|||
|
|||
![]()
Which brings us to (in my humble opinion) the root of most headaches with
computers - security. There are other huge headaches, to be sure, like constantly changing standards, changing interfaces (whatever happened to the standard menu bar through which you could figure out any app almost instantly?), compatibility (backwards, forwards, inter & intra), proprietariness (is that a word?), and awkward copy protection or locking down of a system (rooting / jailbreaking / non-portability of Windows, etc.) To me, security, the headaches caused by those looking to spy or maliciously hack, and all the wasted cycles trying to fight it, is the biggest drag that ever afflicted computing! If anyone knows how one might get MS System Center Endpoint Protection to give up the details on exactly which module(s) / line(s) of code it doesn't like. For now I at least have a workaround in that I can just test my workbook one module at a time with VirusTotal.com (thanks Peter T!)... 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! |
Reply |
Thread Tools | Search this Thread |
Display Modes | |
|
|
![]() |
||||
Thread | Forum | |||
"compile error in hidden module": DISTMOD -- ideas to fix it?? | Excel Discussion (Misc queries) | |||
Finding the earliest "Last Saved Date" of Excel workbooks | Excel Programming | |||
Excel: Narrow print area to wrap to 2nd "column" on page | Excel Discussion (Misc queries) | |||
use variable in Workbooks("book1").Worksheets("sheet1").Range("a1" | Excel Programming |