Why? does cmdButton (ActiveX) _click, that drives NO procedure, interfere with independent sub: AlertResponse = 1; ThisDocument.Saved = True; ThisDocument.Close
During a pilot expt in VBA to test automated closure of a visio doc (with and without ThisDocument.Save /ThisDocument.Saved=1 ), I set up an ** activeX command button ** on the visio drawing page to drive changes in variables (eg shape.text and variables within shapesheet User Sections). This was to provide a test the effectiveness of the .Save method and .Saved = 1 property (code below).
I was surprised to find that clicking an ** activeX command button **, just once, stopped Sub CloseNoSave() from functioning (the doc did not close). This occurred even when the sub for the activeX button_click event contained NO content code (eg, no call to drive another procedure).
The activeX button did not affect the function of Sub CloseWithSave().
I found that UserForm cmd buttons had NO such effect, and did successfully drive Sub CloseWithSave() and Sub CloseNoSave() from the respective _Click event procedures in the UserForm code.
Though the userForm approach is my FIRST choice approach, can you tell me what the problem is with the ActiveX button, and how to avoid it (whilst retaining the service of the activeX button when it is essential)?
[Transfer of Sub CloseNoSave() into the content code of the activeX button_click event sub made no improvement.]
THE CODE follows for "Close With Save" and "Close No Save".
UserForm1 provided a check that userForm cmd buttons did not interfer with "Close With Save" and "Close No Save".
Sub CloseWithSave()
If Not UserForm1 Is Nothing Then Unload UserForm1
Debug.Print "Close With Save"
Application.AlertResponse = 1
ThisDocument.Save
ThisDocument.Close
'Application.Quit
End Sub
Sub CloseNoSave()
If Not UserForm1 Is Nothing Then Unload UserForm1
Debug.Print "Close No Save"
Application.AlertResponse = 1
ThisDocument.Saved = True
ThisDocument.Close
'Application.Quit
End Sub
Sub showForm()
UserForm1.Show
End Sub
I was surprised to find that clicking an ** activeX command button **, just once, stopped Sub CloseNoSave() from functioning (the doc did not close). This occurred even when the sub for the activeX button_click event contained NO content code (eg, no call to drive another procedure).
The activeX button did not affect the function of Sub CloseWithSave().
I found that UserForm cmd buttons had NO such effect, and did successfully drive Sub CloseWithSave() and Sub CloseNoSave() from the respective _Click event procedures in the UserForm code.
Though the userForm approach is my FIRST choice approach, can you tell me what the problem is with the ActiveX button, and how to avoid it (whilst retaining the service of the activeX button when it is essential)?
[Transfer of Sub CloseNoSave() into the content code of the activeX button_click event sub made no improvement.]
THE CODE follows for "Close With Save" and "Close No Save".
UserForm1 provided a check that userForm cmd buttons did not interfer with "Close With Save" and "Close No Save".
Sub CloseWithSave()
If Not UserForm1 Is Nothing Then Unload UserForm1
Debug.Print "Close With Save"
Application.AlertResponse = 1
ThisDocument.Save
ThisDocument.Close
'Application.Quit
End Sub
Sub CloseNoSave()
If Not UserForm1 Is Nothing Then Unload UserForm1
Debug.Print "Close No Save"
Application.AlertResponse = 1
ThisDocument.Saved = True
ThisDocument.Close
'Application.Quit
End Sub
Sub showForm()
UserForm1.Show
End Sub
ASKER
gowFlow, thank you. I've uploaded the visio vsdm file to EE stuff, and received this receipt:
-----------------
Your file has successfully been uploaded!
To download the file, you must be logged into EE-Stuff. Here are two pages that will display your file, if logged in:
View all files for Question ID: 28399775
https://filedb.experts-exchange.com/incoming/ee-stuff/8344-Close-and-Save-visio-doc-27032.vsdm
Direct link to your file
https://filedb.experts-exchange.com/incoming/ee-stuff/8344-Close-and-Save-visio-doc-27032.vsdm
-----------------
Kelvin
-----------------
Your file has successfully been uploaded!
To download the file, you must be logged into EE-Stuff. Here are two pages that will display your file, if logged in:
View all files for Question ID: 28399775
https://filedb.experts-exchange.com/incoming/ee-stuff/8344-Close-and-Save-visio-doc-27032.vsdm
Direct link to your file
https://filedb.experts-exchange.com/incoming/ee-stuff/8344-Close-and-Save-visio-doc-27032.vsdm
-----------------
Kelvin
Oops you mentioned the Excel zone but your file is a Visio ? I did not chk the link. Is your code in Visio or Excel ?
gowlfow
gowlfow
ASKER
The code is visio 2013. Do you deal with visio? If not, I can transfer it to excel and check if the activeX effect persists.
Kelvin
Kelvin
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
ASKER
gowflow,
I have checked out if this ActiveX effect occurs in Excel, and it does NOT!
The method for turning off Alerts differs between the two apps:
Excel uses Application.DisplayAlerts = False to turn off Alerts, whereas
Visio uses Application.AlertResponse = 1 to avoid Alerts (? saying 'its done, so dont do it'..?)
EE have yet to enable Visio 2013 files to be uploaded as one would prefer within this interface, hence the round about route via EE Stuff.
This question should have been more clearly labelled, with 'VISIO' in the title; I'll edit and submit as a new question.
I sign off this question with thanks for your quick response, and look forward to the opportunity of future contact.
Kelvin
I have checked out if this ActiveX effect occurs in Excel, and it does NOT!
The method for turning off Alerts differs between the two apps:
Excel uses Application.DisplayAlerts = False to turn off Alerts, whereas
Visio uses Application.AlertResponse = 1 to avoid Alerts (? saying 'its done, so dont do it'..?)
EE have yet to enable Visio 2013 files to be uploaded as one would prefer within this interface, hence the round about route via EE Stuff.
This question should have been more clearly labelled, with 'VISIO' in the title; I'll edit and submit as a new question.
I sign off this question with thanks for your quick response, and look forward to the opportunity of future contact.
Kelvin
ASKER
with compliments
Kelvin4
Kelvin4
well tks your response but in Visio it shouldn't be different from Excel try
Application.AlertResponse = False
and by the way this is not what prevent the execution of the ActiveX in Excel it is this instruction the will not allow execution of any event until the current one is completed
Application.EnableEvents = False
Usually in Excel when we have a routine that we do not want any interference with other subroutine we do it this way:
gowflow
Application.AlertResponse = False
and by the way this is not what prevent the execution of the ActiveX in Excel it is this instruction the will not allow execution of any event until the current one is completed
Application.EnableEvents = False
Usually in Excel when we have a routine that we do not want any interference with other subroutine we do it this way:
Sub MySub
---> Disable Events
With Application
.EnableEvents = False
.ScreenUpdating = False
.DisplayAlerts = False
End With
...
your code
...
'---> Enable Events
With Application
.EnableEvents = True
.ScreenUpdating = True
.DisplayAlerts = True
End With
End Subgowflow
gowflow