Stop Symantec AV from quarantine my VBA

[EagleOne@microsoftdiscussiongroups]

Excel 2003 up to date

What type of commands in Excel VBA does NAV assume relate to the Bloodhound
Macro Virus.

I assume that it does not like any command that deletes files - but there
may be others.

Can anyone help me strip my Personal.xls of VBA commands which causes NAV to
delete the file?

Any ideas? Plea..........se!

EagleOne

 

[Bernie Deitrick]

It dislikes any use of the VBIDE extensibility - changing code with code is a hallmark of document
viruses. You can set NAV Bloodhound feature to ignore certain files or folders - not sure how, but
my IT department was able to protect my files from being deleted.

HTH,
Bernie
MS Excel MVP

 

[EagleOne@microsoftdiscussiongroups]

Thanks Bernie.

My IT department makes no exceptions, so far.

Would you mind being a bit more specific re: changing code with code; just
an example or two.

Further, I will demonstrate my relative VBA inexperience as to - VBIDE
extensibility?

I thought the problem was related to file delete commands.

 

[Bernie Deitrick]

You can use code like this to add VBA code to a workbook:

Sub AddMeanModuleAndWickedProcedure()

Dim newVBComp As VBComponent
Set newVBComp = ActiveWorkbook.VBProject.VBComponents.Add(vbext_ct_StdModule)
newVBComp.Name = "ReallyDangerousCode"

With newVBComp.CodeModule
.InsertLines .CountOfLines + 1, _
"Sub myKillerSub()" & Chr(13) & _
" Msgbox ""Hello There, I'm about to destroy your computer.... HA HA HA HA!!!!"" "
& Chr(13) & _
"End Sub"
End With
End Sub

It requires a reference to the MS VBA Extensibility X.X (Sorry, I mis-spoke when I said VBIDE
Extensibility) to work, and this was the basis of that Word virus that made headlines 5 years or so
ago. You can see where adding code to workbooks can be problematic, especially if the code is
written in a way that it writes itself into all open workbooks, which then write code to....

Bloodhound may also look for file deletion or kill commands.. I'm not certain of what it looks for,
but I lost lots of code like that above when I was writing a utility that would update the code in
files created from a template....

HTH,
Bernie
MS Excel MVP

 

[EagleOne@microsoftdiscussiongroups]

Outstanding answer!! Thanks

You can use code like this to add VBA code to a workbook:

Sub AddMeanModuleAndWickedProcedure()

Dim newVBComp As VBComponent
Set newVBComp = ActiveWorkbook.VBProject.VBComponents.Add(vbext_ct_StdModule)
newVBComp.Name = "ReallyDangerousCode"

With newVBComp.CodeModule
.InsertLines .CountOfLines + 1, _
"Sub myKillerSub()" & Chr(13) & _
" Msgbox ""Hello There, I'm about to destroy your computer.... HA HA HA HA!!!!"" "
& Chr(13) & _
"End Sub"
End With
End Sub

It requires a reference to the MS VBA Extensibility X.X (Sorry, I mis-spoke when I said VBIDE
Extensibility) to work, and this was the basis of that Word virus that made headlines 5 years or so
ago. You can see where adding code to workbooks can be problematic, especially if the code is
written in a way that it writes itself into all open workbooks, which then write code to....

Bloodhound may also look for file deletion or kill commands.. I'm not certain of what it looks for,
but I lost lots of code like that above when I was writing a utility that would update the code in
files created from a template....

HTH,
Bernie
MS Excel MVP