Any way to stop Access Project Warnings while running VBA?

E

EagleOne

2007/2003

VBA procedures which run fine in 2003 are being interrupted by Macro warnings in 2007. Is there any
way to stop in 2007?

The specific commands which are causing the 5 alerts separate are:

DoCmd .TransferDatabase acExport, "Microsoft Access", myPath & dbsfilename, acQuery, _
"CHOOSE_Add_Fields", "CHOOSE_Add_Fields"
DoCmd .TransferDatabase acExport, "Microsoft Access", myPath & dbsfilename, acQuery, _
"CHOOSE_Revised", "CHOOSE_Revised"
DoCmd .TransferDatabase acExport, "Microsoft Access", myPath & dbsfilename, acQuery, _
"CHOOSE_STARS_UMD", "CHOOSE_STARS_UMD"
DoCmd .TransferDatabase acExport, "Microsoft Access", myPath & dbsfilename, acQuery, _
"STARS_Revised", "STARS_Revised"
DoCmd .TransferDatabase acExport, "Microsoft Access", myPath & dbsfilename, acQuery, _
"STARS_CHOOSE_UMD", "STARS_CHOOSE_UMD"

TIA EagleOne
 
E

Elwood P Dowd

Improved security, also known as PITA.

Have you considered switching back to Access 2003, where they ran fine?

Otherwise, look for help on "Trusted Location".

Elwood
 
A

Albert D. Kallal

2007/2003

VBA procedures which run fine in 2003 are being interrupted by Macro
warnings in 2007. Is there any
way to stop in 2007?

There is been no change in this regards. Sounds like in 2003 you had turned
warnings off.

You can place a

docmd.SetWarnings False

you code goes here......

Then turn back warnings on

docmd.SetWarnings True

You can also permanently disable the warnings by going into the
options..but,that probably not such a good idea (but, sounds like what you
had done in 2003).
 

Ask a Question

Want to reply to this thread or ask your own question?

You'll need to choose a username for the site, which only take a couple of moments. After that, you can post your question and our members will help you out.

Ask a Question

Top