Hi, I have some multiple macros that turn warnings off at the
beginning of the macro and then turn them back on again at the end of
the macro. However, I am getting the message "The command or action
'Set Warnings' isn't available now." I get the option to click ok,
then to halt the macro. I can't imagine why this would be happening as
setting the warnings on and off is pretty basic functionality. Any
help that someone could offer would be much appreciated as I have this
problem in many macros in the same database.

Thanks a lot!
Brian

Click on 'Show all Actions.'
--
KARL DEWEY
Build a little - Test a little


"Bongard" wrote:

> Hi, I have some multiple macros that turn warnings off at the
> beginning of the macro and then turn them back on again at the end of
> the macro. However, I am getting the message "The command or action
> 'Set Warnings' isn't available now." I get the option to click ok,
> then to halt the macro. I can't imagine why this would be happening as
> setting the warnings on and off is pretty basic functionality. Any
> help that someone could offer would be much appreciated as I have this
> problem in many macros in the same database.
>
> Thanks a lot!
> Brian
>

I'm sorry I posted this question in Google Groups and must have been copied
to this location. Karl, I'm not sure where to find this 'Show All Actions'
but am willing to try just about anything to get rid of these messages. They
are killing our automated cycle daily.

Thanks alot

"KARL DEWEY" wrote:

> Click on 'Show all Actions.'
> --
> KARL DEWEY
> Build a little - Test a little
>
>
> "Bongard" wrote:
>
> > Hi, I have some multiple macros that turn warnings off at the
> > beginning of the macro and then turn them back on again at the end of
> > the macro. However, I am getting the message "The command or action
> > 'Set Warnings' isn't available now." I get the option to click ok,
> > then to halt the macro. I can't imagine why this would be happening as
> > setting the warnings on and off is pretty basic functionality. Any
> > help that someone could offer would be much appreciated as I have this
> > problem in many macros in the same database.
> >
> > Thanks a lot!
> > Brian
> >

What version of Access are you running?
--
KARL DEWEY
Build a little - Test a little


"Bongard" wrote:

> I'm sorry I posted this question in Google Groups and must have been copied
> to this location. Karl, I'm not sure where to find this 'Show All Actions'
> but am willing to try just about anything to get rid of these messages. They
> are killing our automated cycle daily.
>
> Thanks alot
>
> "KARL DEWEY" wrote:
>
> > Click on 'Show all Actions.'
> > --
> > KARL DEWEY
> > Build a little - Test a little
> >
> >
> > "Bongard" wrote:
> >
> > > Hi, I have some multiple macros that turn warnings off at the
> > > beginning of the macro and then turn them back on again at the end of
> > > the macro. However, I am getting the message "The command or action
> > > 'Set Warnings' isn't available now." I get the option to click ok,
> > > then to halt the macro. I can't imagine why this would be happening as
> > > setting the warnings on and off is pretty basic functionality. Any
> > > help that someone could offer would be much appreciated as I have this
> > > problem in many macros in the same database.
> > >
> > > Thanks a lot!
> > > Brian
> > >

I am running Access 2003. I'll give you some more info to see if this will
help narrow the problem.

The database is converted from and Access 2000 database.
Along with the 'Set Warnings' command, the 'OutputTo' command is producing
the same kind of errors when ran either through a macro or VBA.
I have a bunch of macros running similar commands in my automation, and for
some reason it isn't consistent about where it errors out each time.
If I run the individual macros manually, they never error out.

The VBA references that I have enabled are as follows:
Visual Basic fort Applications
Microsoft Access 11.0 Object Library
OLE Automation
Microsoft DAO 3.6 Object Library
Microsoft ActiveX Data Objects 2.5 Library

Thanks a lot

I do not know this area but here are post by Douglas J. Steele that might
apply. I would back up the database first.

Are your References okay? (while in the VB Editor, select Tools |
References from the menu bar. Make sure none of the selected references--the
ones with check marks in front of them at the top of the list--have MISSING:
in front of them)

Try adding another reference at random, backing out of the References
dialog, then going back in and deleting the reference you just added.

If that still doesnt' work, write down all of the references you currently
have selected. Unselect as many as you can (Access won't let you unselect
them all), then back out of the dialog. Go back in and reselect all of the
ones you succeeded in deleting. (Note: They'll be in alphabetic order, not
at the top anymore!)


--
KARL DEWEY
Build a little - Test a little


"Bongard" wrote:

>
> I am running Access 2003. I'll give you some more info to see if this will
> help narrow the problem.
>
> The database is converted from and Access 2000 database.
> Along with the 'Set Warnings' command, the 'OutputTo' command is producing
> the same kind of errors when ran either through a macro or VBA.
> I have a bunch of macros running similar commands in my automation, and for
> some reason it isn't consistent about where it errors out each time.
> If I run the individual macros manually, they never error out.
>
> The VBA references that I have enabled are as follows:
> Visual Basic fort Applications
> Microsoft Access 11.0 Object Library
> OLE Automation
> Microsoft DAO 3.6 Object Library
> Microsoft ActiveX Data Objects 2.5 Library
>
> Thanks a lot

I did find his post in another forum somewhere while searching Google. I
don't have references that are showing up as "missing" or "broken."

Also, I followed his second set of instructions, deleted the bottom three
and re-added them in the same priority order that they were in before.

I guess I will know tomorrow morning if this does anything when the
automated processes run again.

I'll keep you posted.

I had the same issues happen again this morning. Today it actually killed
twice during the automated process - Once with the message "The command or
aaction "OutputTo" isn't available now" and once with the message "The
command or action 'Set Warnings' isn't available now." I am puzzeled to say
the least - Again, any help or ideas would be much appreciated.

Thanks a lot,
Brian