Access AutoExec Macro: Virus Danger? 2

[jjlogan]

I would like to create a macro that maximizes the database window upon opening my multi-user database program. I learned about naming the macro AutoExec so Access will auto expand the window, but Web references mention danger of virus intrusion into the AutoExec.
Question: Would I be making my Access (2000) application MORE SUSCEPTIBLE to a virus attack by having AutoExec macro, or does the virus attacks just create a new AutoExec (i.e. the attack is not looking for AutoExec, it just creates it). The attacks I am referring to are documented on web sites; these viruses are specific to Access and use the AutoExec macro to do other stuff like infect all other .mdb files on same folder.
Thanks for any input before I add this automation to my application. Jeff

 

[StuckInTheMiddle]

Having an autoexec macro in your MDB does not make you any greater of a target for this type of virus.

The warnings you are reading refer to you opening a MDB with an autoexec macro in it that's written to do malicious things.

It's possibly for instance that someone could write a autoexec to copy itself to all MDBs on your hard drive, in which case it wouldn't matter if you already had one in there or not.

This is just my opinion; seek professional advice if really worried

 

[jjlogan]

Thanks for the input, StuckInTheMiddle. I posted this question because after spending a lot of time viewing google threads, not one "expert" site answered this question about whether risk is greater if have an AutoExec. The sites just talked about what this AutoExec virus does and that it operates out of AutoExec (of course because this macro is forced to run upon opening).
So, from your experience, you sounded confident that the virus (or hacker) sets up own AutoExec (or overrides yours) if they get access in first place? Also, virus warning noted mainly Access 97 susceptible; however I would not rest on that.
If I were to check with "expert" - do you have any recommendations on who or where to find them?
Thanks again for any info you could provide.
Jeff

 

[xlbo]

Having an autoexec macro does not put your database in any more danger than not having it. If a hacker / virus manages to get access to your db, they will do want they want with it autoexec or not.

Hackers and virii should be stopped by the network 1st and only secondarily by the database.

 

[jjlogan]

Thanks xlbo for the confirmation. That answered by question that just would not go away. And your point about the network security as first line of defense helps present the larger picture. We are now backing up our database on regular intervals also.
Thanks again.
Jeff