how to set answer = to command button

[Jake975]

how do i get this code to wait for a command button click first?

Sub ProcessnaTEST()
'Dim answer As NightAuditP.Button1.Caption
'answer = buttonText

Call intprogress

NightAuditP.Question.Caption = ("Are you ready to start the night audit file process?" & vbNewLine _
& "This is for the date of: " & Format(Date - 1, "mm-dd-yyyy"))
 
  If answer = Yes Then
'  Call PNT2
  MsgBox "Nihgt Audit Checklist printed"
  'Call pmtpause
  'Call Makefolder
  'Call FolderPicker
   ' Call Msgbox_1A
  ElseIf answer = vbNo Then
    MsgBox "Click Start prior to running audit in Opera when ready.", , "Night Audit Processing"
  Else
    'Call Reset
  End If
  End Sub

 

[GWteB]

I have looked at your workbook and have a few notes regarding your implementation of the progress bar.
I feel that you understand how to apply it (technically). However, in general, you obviously do not want the dynamic display of a progress bar to seriously slow down the process you perform through VBA. In addition, it can be nice to remain flexible with regard to some procedures. What I have seen is that you have converted quite a few procedures to expect the mandatory arguments argUSF and argSteps when called. The MakeFolder and FolderPicker procedures are examples of this. This can be at the expense of flexibility (after all, only to be called with valid arguments from the userform) or readability of your code (to be called from anywhere with fake arguments, such as argUSF: = Nothing and argSteps: = 0).
Furthermore, I would recommend leaving the progress bar update code outside small For / Next loops, especially where worksheet ranges are addressed. In addition, this cannot be otherwise in procedures where several loops occur, after all how do you determine the total ratio of all three loops together in advance? In this regard, I refer to the example procedures TASK_Example_41 to 44.
So it's about making a well-considered decision about the places within your code wether to force an update of the progress bar or not. The right balance between performance, flexibly applicable and readable code and an informative gadget can often only be found by simply trying it out.

 

[Jake975]

thank you so much for your time and feedback. This has been a long journey. And to think many of the things done with this workbook used to be done manually. There are so many different parts involved as you see and with this going to be deployed for business use you understand when i say it has to be "stupid proof". I really thank you for helping. I will defiantly keep you posted on the progress.

 

[GWteB]

You are welcome @Jake975, appreciate your feedback.
Btw making applications ? proof can be a real challenge sometimes