Macro Using "Output to"

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

Guest

I have finally mastered using the "output to" function of a macro to a specfic file that includes the month # (mm) in the file name. In the event I need to re-run the macro and re-generate the file....Is the a way to avoid the need to answer the question " This file already exist Do you want to replace it?
TI
Roger
 
Roger,

Before the OutputTo action, insert an action SetWarnings, arguments: False
Make sure to include another to reverse this (arguments: True) after the
OutputTo action, or Access will do everything without asking for
confirmation thereafter!

HTH,
Nikos

Roger said:
I have finally mastered using the "output to" function of a macro to a
Click to expand...
specfic file that includes the month # (mm) in the file name. In the event
I need to re-run the macro and re-generate the file....Is the a way to avoid
the need to answer the question " This file already exist Do you want to
replace it?"
 
I know this "setwarnings" works in access but the output file is to a *.rft file to be used by Word. I think the " This file already exist Do you want to replace it?" warning is coming from word or windows in general
I have tried setwarning both ways an still get the warning
Roge


----- Roger wrote: ----

I have finally mastered using the "output to" function of a macro to a specfic file that includes the month # (mm) in the file name. In the event I need to re-run the macro and re-generate the file....Is the a way to avoid the need to answer the question " This file already exist Do you want to replace it?
TI
Roger
 
Roger
I had this same problem, but nobody seemed to have an answer. Finally I have one! Somebody was having the exact opposite problem as us, but he was using VB code. The code and method is really easy to use

If you are running it off of a button, in the On Click event for the button properties, select event procedure
Next select the build button. This should take you into the VB code editor. Your function should look something like this

Private Sub Command10_Click(
DoCmd.RunMacro ("MacroName") 'Note: Must include " " around macro nam

End Su

I tried this out on my own macro, and it works great. Hope it helps
Will
 
Back
Top