DoCmd.SetWarnings False
BE CAREFUL!!!
Also use an exit procedure and error handler that redirects to it... and be
SURE to turn DoCmd.SetWarnings True in the exit procedure of the
sub/function. You don't want to accidently leave this off.
Alternatively, use CurrentDb.Execute <query> instead, which by design gives
no warnings. The drawback here is that you can't use the Expression Service.
On the plus side, dbFailOnError as the second argument will throw an
trappable error, which you can't get with DoCmd.RunSQL
--
Jack Leach
www.tristatemachine.com
"I haven''t failed, I''ve found ten thousand ways that don''t work."
-Thomas Edison (1847-1931)
