hi, is there a way to test that there is something to undo before executing
an Application.Undo?

Thanks,
pwrob
--
xl help seeker

This works ok in xl2003 in my USA/English version:

If Application.CommandBars("Standard").Controls("Undo ").Enabled = True Then
MsgBox "there's something to undo"
Else
MsgBox "nothing to undo"
End If



pwrob wrote:

hi, is there a way to test that there is something to undo before executing
an Application.Undo?

Thanks,
pwrob
--
xl help seeker

--

Dave Peterson

On Error Resume Next
ud = Application.CommandBars.FindControl(ID:=128).ListC ount
' could test for err.number, if 0 but ud=0
' probably means Redo has at least 1 item that'll
' get called with app.undo
On Error GoTo 0

Even though Commandbars are replaced with the Ribbon in 2007 this still
appears to work in 2007

If the intention is to call .Undo but you're only concerned about an error
if Undo is empty, just do simply

On error resume next
Application.Undo
On error goto 0

Regards,
Peter T


"pwrob" wrote in message
...
hi, is there a way to test that there is something to undo before
executing
an Application.Undo?

Thanks,
pwrob
--
xl help seeker

great, thank you very much. cheers, pwrob
--
xl help seeker


"Dave Peterson" wrote:

This works ok in xl2003 in my USA/English version:

If Application.CommandBars("Standard").Controls("Undo ").Enabled = True Then
MsgBox "there's something to undo"
Else
MsgBox "nothing to undo"
End If



pwrob wrote:

hi, is there a way to test that there is something to undo before executing
an Application.Undo?

Thanks,
pwrob
--
xl help seeker

--

Dave Peterson
.

thank you for the prompt reply.

i know the app undo throws error 1004 if there is nothing to undo and i'm a
bit concerned that something else might throw the same error...

do you know whether i can place the on error resume next statement in the
middle of my sub? if so, will it apply to all code thereafter or from the
beginning of the sub?

thanks,
pwrob

--
xl help seeker


"Peter T" wrote:

On Error Resume Next
ud = Application.CommandBars.FindControl(ID:=128).ListC ount
' could test for err.number, if 0 but ud=0
' probably means Redo has at least 1 item that'll
' get called with app.undo
On Error GoTo 0

Even though Commandbars are replaced with the Ribbon in 2007 this still
appears to work in 2007

If the intention is to call .Undo but you're only concerned about an error
if Undo is empty, just do simply

On error resume next
Application.Undo
On error goto 0

Regards,
Peter T


"pwrob" wrote in message
...
hi, is there a way to test that there is something to undo before
executing
an Application.Undo?

Thanks,
pwrob
--
xl help seeker


.

hi again, just realized that ...goto 0 disables the error handling - this
will work! thanks again - cheers, pwrob
--
xl help seeker


"Peter T" wrote:

On Error Resume Next
ud = Application.CommandBars.FindControl(ID:=128).ListC ount
' could test for err.number, if 0 but ud=0
' probably means Redo has at least 1 item that'll
' get called with app.undo
On Error GoTo 0

Even though Commandbars are replaced with the Ribbon in 2007 this still
appears to work in 2007

If the intention is to call .Undo but you're only concerned about an error
if Undo is empty, just do simply

On error resume next
Application.Undo
On error goto 0

Regards,
Peter T


"pwrob" wrote in message
...
hi, is there a way to test that there is something to undo before
executing
an Application.Undo?

Thanks,
pwrob
--
xl help seeker


.