[AccessD] Access no longer prompts

Stuart McLachlan stuart at lexacorp.com.pg
Tue Aug 17 19:13:00 CDT 2004


On 17 Aug 2004 at 16:12, Andy Lacey wrote:

> Or it could be that a routine somewhere sets warnings off and doesn't set
> them back on. You can soon prove this by knocking up a macro that does a
> SetWarnings True or a function that just does a DoCmd.Setwarnings True, then
> running it

Or just do a Ctrl+G and enter "Docmd.Setwarnings True" in the Immediate
Window.
-- 
Stuart





More information about the AccessD mailing list