Which annoying popup message are you talking about? OutputTo doesn't
necessarily give a message. Please post the code you are using and the
message you're talking about.
It's of the form: "Outputing report such-and-such to file such-and-such".
Actually, it's not really a popup, but an informational one that appears and
disappears.
You could try
DoCmd SetWarnings False
before the OutputTo command, but don't forget to put
DoCmd SetWarnings True
after it, or you will be wondering why all sorts of bad things are
happening and you aren't being told about them!
Access may or may not consider a transient informational message that
does not require a user response as a "Warning".
It's of the form: "Outputing report such-and-such to file such-and-such".
Actually, it's not really a popup, but an informational one that appears and
disappears.
I tried Docmd.SetWarnings False/True and it didn't help. Guess I am stuck
with yet another Microsoft "feature". I wonder if these people ever actually
try to use what they create.
I tried Docmd.SetWarnings False/True and it didn't help. Guess I am
stuck
with yet another Microsoft "feature". I wonder if these people ever
actually
try to use what they create.
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.