Macro Secuity and Command Line

  • Thread starter Thread starter Guest
  • Start date Start date
G

Guest

All,
We recently upgrade from Access 2000 to 2003. With the warning now appearing
when DB opens the batch files I used previsouly in conjunction with Window's
Scheduler aren't dong much for me. :) I don't know a way around this to
either accept or supress it. I'd like to stick with the batch files if I can.
I've seen a solution with VBE, but I have little knowledge how to mesh the
two (VBE & batch files) together. Any suggestions?

Thank you greatly any insight!
 
Back
Top