Learn how to use and navigate the new features included in Bootstrap 4, the most popular HTML, CSS, and JavaScript framework for developing responsive, mobile-first websites.
A VBA Progress Bar for Excel and Other Microsoft Apps.
Published on
61,887 Points
Keeping the user informed is important
If you have written some VBA code for Excel (or Word, or Access), and it takes a long time to execute, it is important to keep the user informed that the code is progressing. Psychologically, it can also have a tremendously positive effect on the perceived responsiveness and speed of your program if the user can see a visual representation of the current progress.
Common methods of keeping the user informed
Currently, a lot of people keep the user informed by allowing the actions of the macro to be seen. (i.e., the flicker of sheets being activated, cells being changed, etc...). This is generally a terrible idea unless the whole routine is finished very quickly. Excel experts should have learned by now that by setting Application.ScreenUpdating
Now that Excel's interface is frozen to speed up procedures, it's especially important to inform the user. Many people do this by setting the value of Application.StatusBar. This can hold any text, and updates even when screen updating is disabled. By changing this regularly, the programmer can give a play by play of the current position in the code, or display a percentage completion in a large loop.
Something truly impressive
If you want a great tool for keeping the user informed you should create a progress bar form, show the form before beginning code execution, and hide it afterwards. This is something you could do yourself, but to get you started, I've been employing and improving on my own custom progress bar for quite some time now. I think you should find it useful and very customizable:
Features
Using the progress bar practically
You are responsible for picking an appropriate minimum and maximum value. For instance, if you are looping over R rows (from 1 to R) and C columns (from 1 to C), you should set the minimum to 0 and the maximum to ( R*C ). Furthermore, if you are currently on row i and column j, (and you are looping over all rows within each column), you should be setting the current value to [ i + (j-1)*R ]
If the cancel button is being displayed, you are responsible for periodically checking whether or not the cancel button has been pressed. Do this by checking whether ProgressDialogue.cancelIsP
The following code block shows the function calls you should remember to include in your loops when using the progress bar dialogue:
This produces the following progress bar:
If you are looping over code where you are making a large number of iterations over code that is very quick to execute, then you might find that updating the dialogue becomes your bottleneck. To prevent this, you can only update the progress bar periodically, using a quick check. For instance, you can say:
If index MOD 1000 = 0 Then ProgressDialogue.SetValue(
This way, the dialogue will only get updated every 1000 loops, and it will have much less impact on your code. You will want to play around with how often you update it, to balance the refresh rate with the amount of time spent updating the progress bar. Ideally, in other applications, a progress bar is kept up to date in a thread, but VBA has no support for threading.
Implemented Example and Code
Here, I've attached a workbook containing the 'wasting time' example above. You can use this to experiment with the ProgressDialogue form, and take a look at its implementation.
Progress-Bar-Example.xls
For convenience, I've also included in this article the code within the ProgressDialogue class:
Because .frm and .frx files cannot be attached on experts-exchange, I cannot provide you with those directly, but you can easily add this progress bar to any project by following these steps:
1. Download the example excel file above
2. Open the file, and open the VBA project (Alt+F11)
3. Export the ProgressDialogue form. (Save it somewhere you will remember in 5 seconds).
4. Import the exported file in any other excel project. (You can now delete the exported .frm and .frx files from your system.)
Remember that this same concept can be adapted to other Microsoft Applications, Excel is simply where I've built it here.
Building pleasant user interfaces is crucial to the success and reception of your VBA applications and I think this progress bar dialogue can go a long way to improving that. Feel free to use these ideas and code, and build on them. I wish you success!
--
Alain Bryden
References
Progress bar with a user form in Excel - http://support.microsoft.c
GetTickCount system function in VBA - http://msdn.microsoft.com/
Interfaced-Progress-Bar-Example.xls
If you have written some VBA code for Excel (or Word, or Access), and it takes a long time to execute, it is important to keep the user informed that the code is progressing. Psychologically, it can also have a tremendously positive effect on the perceived responsiveness and speed of your program if the user can see a visual representation of the current progress.
Common methods of keeping the user informed
Currently, a lot of people keep the user informed by allowing the actions of the macro to be seen. (i.e., the flicker of sheets being activated, cells being changed, etc...). This is generally a terrible idea unless the whole routine is finished very quickly. Excel experts should have learned by now that by setting Application.ScreenUpdating
Now that Excel's interface is frozen to speed up procedures, it's especially important to inform the user. Many people do this by setting the value of Application.StatusBar. This can hold any text, and updates even when screen updating is disabled. By changing this regularly, the programmer can give a play by play of the current position in the code, or display a percentage completion in a large loop.
Something truly impressive
If you want a great tool for keeping the user informed you should create a progress bar form, show the form before beginning code execution, and hide it afterwards. This is something you could do yourself, but to get you started, I've been employing and improving on my own custom progress bar for quite some time now. I think you should find it useful and very customizable:
Features
Programmer can configure the progress bar with one function call, then all that is needed to update is to call SetValue.
The progress bar's position and percentage label are automatically computed based on the minimum, maximum, and last set value.
The status (caption above the progress bar) can be set dynamically to indicate additional information, such as the current stage of execution.
An optional cancel button allows the user a mechanism to halt your lengthy process. The cancel button text can also be set, for instance to "Stop" or "Cancel Generation". The default caption is "Cancel". If set to vbNullString, the cancel button is hidden entirely.
An optional label can show the time elapsed since the dialogue box was configured. (It is assumed that you will configure the dialogue directly before showing it). If this option is disabled, the progress bar update routine will not waste time in computing the elapsed time.
An optional label can estimate the time remaining before completion. This is a very accurate estimate if you have appropriately set the min and max values. (You can test this in the example below.) This can be disabled, in which case no time is wasted in computing the remaining time.
Your calling routine can get the current value of the progress bar, as well as the formatted run time. I use this, for instance, for logging, or to display on the status bar the final run time of the routine after it is complete. 
Using the progress bar practically
You are responsible for picking an appropriate minimum and maximum value. For instance, if you are looping over R rows (from 1 to R) and C columns (from 1 to C), you should set the minimum to 0 and the maximum to ( R*C ). Furthermore, if you are currently on row i and column j, (and you are looping over all rows within each column), you should be setting the current value to [ i + (j-1)*R ]
If the cancel button is being displayed, you are responsible for periodically checking whether or not the cancel button has been pressed. Do this by checking whether ProgressDialogue.cancelIsP
The following code block shows the function calls you should remember to include in your loops when using the progress bar dialogue:
Sub wasteTime()
Dim i As Long
Dim diag As New ProgressDialogue
diag.Configure "Wasting Time", "Now wasting your time...", -10000, 10000
diag.Show
For i = -10000 To 10000
diag.SetValue i
diag.SetStatus "Now wasting your time... " & i
If diag.cancelIsPressed Then Exit For
Next i
diag.Hide
End Sub
This produces the following progress bar:
If you are looping over code where you are making a large number of iterations over code that is very quick to execute, then you might find that updating the dialogue becomes your bottleneck. To prevent this, you can only update the progress bar periodically, using a quick check. For instance, you can say:
If index MOD 1000 = 0 Then ProgressDialogue.SetValue(
This way, the dialogue will only get updated every 1000 loops, and it will have much less impact on your code. You will want to play around with how often you update it, to balance the refresh rate with the amount of time spent updating the progress bar. Ideally, in other applications, a progress bar is kept up to date in a thread, but VBA has no support for threading.
Implemented Example and Code
Here, I've attached a workbook containing the 'wasting time' example above. You can use this to experiment with the ProgressDialogue form, and take a look at its implementation.
Progress-Bar-Example.xls
For convenience, I've also included in this article the code within the ProgressDialogue class:
Option Explicit
Dim Cancelled As Boolean, showTime As Boolean, showTimeLeft As Boolean
Dim startTime As Long
Dim BarMin As Long, BarMax As Long, BarVal As Long
Private Declare Function GetTickCount Lib "Kernel32" () As Long
'Title will be the title of the dialogue.
'Status will be the label above the progress bar, and can be changed with SetStatus.
'Min is the progress bar minimum value, only set by calling configure.
'Max is the progress bar maximum value, only set by calling configure.
'CancelButtonText is the caption of the cancel button. If set to vbNullString, it is hidden.
'optShowTimeElapsed controls whether the progress bar computes and displays the time elapsed.
'optShowTimeRemaining controls whether the progress bar estimates and displays the time remaining.
'calling Configure sets the current value equal to Min.
'calling Configure resets the current run time.
Public Sub Configure(ByVal title As String, ByVal status As String, _
ByVal Min As Long, ByVal Max As Long, _
Optional ByVal CancelButtonText As String = "Cancel", _
Optional ByVal optShowTimeElapsed As Boolean = True, _
Optional ByVal optShowTimeRemaining As Boolean = True)
Me.Caption = title
lblStatus.Caption = status
BarMin = Min
BarMax = Max
BarVal = Min
CancelButton.Visible = Not CancelButtonText = vbNullString
CancelButton.Caption = CancelButtonText
startTime = GetTickCount
showTime = optShowTimeElapsed
showTimeLeft = optShowTimeRemaining
lblRunTime.Caption = ""
lblRemainingTime.Caption = ""
Cancelled = False
End Sub
'Set the label text above the status bar
Public Sub SetStatus(ByVal status As String)
lblStatus.Caption = status
DoEvents
End Sub
'Set the value of the status bar, a long which is snapped to a value between Min and Max
Public Sub SetValue(ByVal value As Long)
If value < BarMin Then value = BarMin
If value > BarMax Then value = BarMax
Dim progress As Double, runTime As Long
BarVal = value
progress = (BarVal - BarMin) / (BarMax - BarMin)
ProgressBar.Width = 292 * progress
lblPercent = Int(progress * 10000) / 100 & "%"
runTime = GetRunTime()
If showTime Then lblRunTime.Caption = "Time Elapsed: " & GetRunTimeString(runTime, True)
If showTimeLeft And progress > 0 Then _
lblRemainingTime.Caption = "Est. Time Left: " & GetRunTimeString(runTime * (1 - progress) / progress, False)
DoEvents
End Sub
'Get the time (in milliseconds) since the progress bar "Configure" routine was last called
Public Function GetRunTime() As Long
GetRunTime = GetTickCount - startTime
End Function
'Get the time (in hours, minutes, seconds) since "Configure" was last called
Public Function GetFormattedRunTime() As String
GetFormattedRunTime = GetRunTimeString(GetTickCount - startTime)
End Function
'Formats a time in milliseconds as hours, minutes, seconds.milliseconds
'Milliseconds are excluded if showMsecs is set to false
Private Function GetRunTimeString(ByVal runTime As Long, Optional ByVal showMsecs As Boolean = True) As String
Dim msecs&, hrs&, mins&, secs#
msecs = runTime
hrs = Int(msecs / 3600000)
mins = Int(msecs / 60000) - 60 * hrs
secs = msecs / 1000 - 60 * (mins + 60 * hrs)
GetRunTimeString = IIf(hrs > 0, hrs & " hours ", "") _
& IIf(mins > 0, mins & " minutes ", "") _
& IIf(secs > 0, IIf(showMsecs, secs, Int(secs + 0.5)) & " seconds", "")
End Function
'Returns the current value of the progress bar
Public Function GetValue() As Long
GetValue = BarVal
End Function
'Returns whether or not the cancel button has been pressed.
'The ProgressDialogue must be polled regularily to detect whether cancel was pressed.
Public Function cancelIsPressed() As Boolean
cancelIsPressed = Cancelled
End Function
'Recalls that cancel was pressed so that they calling routine can be notified next time it asks.
Private Sub CancelButton_Click()
Cancelled = True
lblStatus.Caption = "Cancelled By User. Please Wait."
End Sub
Because .frm and .frx files cannot be attached on experts-exchange, I cannot provide you with those directly, but you can easily add this progress bar to any project by following these steps:
1. Download the example excel file above
2. Open the file, and open the VBA project (Alt+F11)
3. Export the ProgressDialogue form. (Save it somewhere you will remember in 5 seconds).
4. Import the exported file in any other excel project. (You can now delete the exported .frm and .frx files from your system.)
Remember that this same concept can be adapted to other Microsoft Applications, Excel is simply where I've built it here.
Building pleasant user interfaces is crucial to the success and reception of your VBA applications and I think this progress bar dialogue can go a long way to improving that. Feel free to use these ideas and code, and build on them. I wish you success!
--
Alain Bryden
References
Progress bar with a user form in Excel - http://support.microsoft.c
GetTickCount system function in VBA - http://msdn.microsoft.com/
Interfaced-Progress-Bar-Example.xls
-
2
2
- +6
11 Comments
alainbryden,
Your article has been selected for the Editors Choice designation, EE's highest honor for articles. Great work!
matthewspatrick
Page Editor
Your article has been selected for the Editors Choice designation, EE's highest honor for articles. Great work!
matthewspatrick
Page Editor
alainbryden,
quite elegant ... this however "If index MOD 1000 = 0 Then ProgressDialogue.SetValue(
here is a very related question that you might be interested in ...
http://www.experts-exchange.com/Software/Office_Productivity/Office_Suites/MS_Office/Excel/Q_27505597.html
quite elegant ... this however "If index MOD 1000 = 0 Then ProgressDialogue.SetValue(
here is a very related question that you might be interested in ...
http://www.experts-exchange.com/Software/Office_Productivity/Office_Suites/MS_Office/Excel/Q_27505597.html
Sure thing:
This is a common way to execute an operation only every X iterations of a loop. Updating the status bar isn't a hugely expensive operation - but if you're looping over relatively fast code thousands and thousands of times, it can quickly become the bottleneck - updating the status can make your process take much longer!
The way to cut down on this overhead is to only update the status every thousand or so loops - just pick a number that gives you a good looking refresh rate, but one so needlessly fast that you're wasting computing power on invisible updates.
MOD is a function which returns the remainder of an integer division. If you divide a number by 1000, the only time the result will be 0 is if the number is a multiple of 1000, so that's why the code will only get executed every 1000 loops.
Hope that helps.
If ( value mod X = 0 )
...
value ++;
This is a common way to execute an operation only every X iterations of a loop. Updating the status bar isn't a hugely expensive operation - but if you're looping over relatively fast code thousands and thousands of times, it can quickly become the bottleneck - updating the status can make your process take much longer!
The way to cut down on this overhead is to only update the status every thousand or so loops - just pick a number that gives you a good looking refresh rate, but one so needlessly fast that you're wasting computing power on invisible updates.
MOD is a function which returns the remainder of an integer division. If you divide a number by 1000, the only time the result will be 0 is if the number is a multiple of 1000, so that's why the code will only get executed every 1000 loops.
Hope that helps.
alainbryden
1st GREAT WORK! I've played with your progress bar within your sample workbook but is there a way you could assist me with the following code below. I'm not an expert with VBA (still have my training wheels on).
I have a code that opens another workbook, copies data from the newly opened workbook and pastes it into the original workbook, then exports the data into Access for storage.
My question is would I update the "progress bar" code to work with the vba shown above.
I downloaded the example workbook, read through your article and for an expert it explains it well but I'm sort of lost because of my inexperience with loops and setting MIN and MAX values for iterations. ((O_O))
Thank you in advance! :)
1st GREAT WORK! I've played with your progress bar within your sample workbook but is there a way you could assist me with the following code below. I'm not an expert with VBA (still have my training wheels on).
I have a code that opens another workbook, copies data from the newly opened workbook and pastes it into the original workbook, then exports the data into Access for storage.
Option Explicit
Function GetData()
Dim MasterWB As Workbook
Dim ws1 As Worksheet
Dim ws2 As Worksheet
Dim loEndUserTable As ListObject
Dim loMasterTable As ListObject
Dim rngIn As Range
Dim rngOut As Range
Dim AccDatabase As Object
Dim FilePath As String
'Open Master Workbook to update Manager's reports********************************************************************************
'*************************************************************************************************************
'Message Box to Inform End User update is about to occur
MsgBox "Please wait while the latest available data is retrieved. This will take a few moments. Thank you for your patience"
Application.Workbooks.Open FileName:="T:\ErrorData\Reporting_Analysis\CLC Productivity\Roaming\RoamingDataBackOffice.xlsm"
With Application
.ScreenUpdating = False
.DisplayAlerts = False
End With
'set Master Workbook
Set MasterWB = Application.Workbooks("RoamingDataBackOffice.xlsm")
'~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ BELOW IS THE COPY FROM WORKBOOK TO WORKBOOK CODE ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
'****************************************************************************************************************************************
'****************************************************************************************************************************************
'AAR **************************************************************************************************************
'Set ThisWorkbook = Application.Workbooks
Set ws1 = MasterWB.Sheets("AAR")
Set loEndUserTable = ws1.ListObjects("AARTracker")
Set rngIn = loEndUserTable.DataBodyRange
' only do it if there are rows in the table
If Not rngIn Is Nothing Then
Set ws2 = ThisWorkbook.Worksheets("AAR")
Set loMasterTable = ws2.ListObjects("AARTracker")
If loMasterTable.DataBodyRange Is Nothing Then
' if no rows yet added to master use the header range
Set rngOut = loMasterTable.HeaderRowRange
Else
Set rngOut = loMasterTable.DataBodyRange
End If
' move the range down to the first empty row in the master table,
' and resize it to be the same as the input range
Set rngOut = rngOut.Offset(rngOut.Rows.Count, 0). _
Resize(rngIn.Rows.Count, rngIn.Columns.Count)
rngIn.Copy
rngOut.PasteSpecial xlPasteValues
' now delete all rows from the input table
loEndUserTable.DataBodyRange.EntireRow.Delete
End If
'****************************************************************************************************************************************
'****************************************************************************************************************************************
'SWAC ***********************************************************************************************************
'Set ThisWorkbook = Application.Workbooks("MPT_EndUser_revised.xlsx")
Set ws1 = MasterWB.Sheets("Swac")
Set loEndUserTable = ws1.ListObjects("SwacTracker")
Set rngIn = loEndUserTable.DataBodyRange
' only do it if there are rows in the table
If Not rngIn Is Nothing Then
Set ws2 = ThisWorkbook.Sheets("Swac")
Set loMasterTable = ws2.ListObjects("SwacTracker")
If loMasterTable.DataBodyRange Is Nothing Then
' if no rows yet added to master use the header range
Set rngOut = loMasterTable.HeaderRowRange
Else
Set rngOut = loMasterTable.DataBodyRange
End If
' move the range down to the first empty row in the master table,
' and resize it to be the same as the input range
Set rngOut = rngOut.Offset(rngOut.Rows.Count, 0). _
Resize(rngIn.Rows.Count, rngIn.Columns.Count)
rngIn.Copy
rngOut.PasteSpecial xlPasteValues
' now delete all rows from the input table
loEndUserTable.DataBodyRange.EntireRow.Delete
End If
'****************************************************************************************************************************************
'****************************************************************************************************************************************
'Spanish Tracker***********************************************************************************************************
'Set ThisWorkbook = Application.Workbooks("MPT_EndUser_revised.xlsx")
Set ws1 = MasterWB.Sheets("Spanish Tracker")
Set loEndUserTable = ws1.ListObjects("SpanishTracker")
Set rngIn = loEndUserTable.DataBodyRange
' only do it if there are rows in the table
If Not rngIn Is Nothing Then
Set ws2 = ThisWorkbook.Sheets("Spanish Tracker")
Set loMasterTable = ws2.ListObjects("SpanishTracker")
If loMasterTable.DataBodyRange Is Nothing Then
' if no rows yet added to master use the header range
Set rngOut = loMasterTable.HeaderRowRange
Else
Set rngOut = loMasterTable.DataBodyRange
End If
' move the range down to the first empty row in the master table,
' and resize it to be the same as the input range
Set rngOut = rngOut.Offset(rngOut.Rows.Count, 0). _
Resize(rngIn.Rows.Count, rngIn.Columns.Count)
rngIn.Copy
rngOut.PasteSpecial xlPasteValues
' now delete all rows from the input table
loEndUserTable.DataBodyRange.EntireRow.Delete
End If
'****************************************************************************************************************************************
'****************************************************************************************************************************************
'Credit Refresh***********************************************************************************************************
'Set ThisWorkbook = Application.Workbooks("MPT_EndUser_revised.xlsx")
Set ws1 = MasterWB.Sheets("Credit Refresh Tracker")
Set loEndUserTable = ws1.ListObjects("creditRefreshTracker")
Set rngIn = loEndUserTable.DataBodyRange
' only do it if there are rows in the table
If Not rngIn Is Nothing Then
Set ws2 = ThisWorkbook.Sheets("Credit Refresh Tracker")
Set loMasterTable = ws2.ListObjects("creditRefreshTracker")
If loMasterTable.DataBodyRange Is Nothing Then
' if no rows yet added to master use the header range
Set rngOut = loMasterTable.HeaderRowRange
Else
Set rngOut = loMasterTable.DataBodyRange
End If
' move the range down to the first empty row in the master table,
' and resize it to be the same as the input range
Set rngOut = rngOut.Offset(rngOut.Rows.Count, 0). _
Resize(rngIn.Rows.Count, rngIn.Columns.Count)
rngIn.Copy
rngOut.PasteSpecial xlPasteValues
' now delete all rows from the input table
loEndUserTable.DataBodyRange.EntireRow.Delete
End If
'****************************************************************************************************************************************
'****************************************************************************************************************************************
'Cancellation ***********************************************************************************************************
'Set ThisWorkbook = Application.Workbooks("MPT_EndUser_revised.xlsx")
Set ws1 = MasterWB.Sheets("Cancellation Request")
Set loEndUserTable = ws1.ListObjects("Cancellation")
Set rngIn = loEndUserTable.DataBodyRange
' only do it if there are rows in the table
If Not rngIn Is Nothing Then
Set ws2 = ThisWorkbook.Sheets("Cancellation Request")
Set loMasterTable = ws2.ListObjects("Cancellation")
If loMasterTable.DataBodyRange Is Nothing Then
' if no rows yet added to master use the header range
Set rngOut = loMasterTable.HeaderRowRange
Else
Set rngOut = loMasterTable.DataBodyRange
End If
' move the range down to the first empty row in the master table,
' and resize it to be the same as the input range
Set rngOut = rngOut.Offset(rngOut.Rows.Count, 0). _
Resize(rngIn.Rows.Count, rngIn.Columns.Count)
rngIn.Copy
rngOut.PasteSpecial xlPasteValues
' now delete all rows from the input table
loEndUserTable.DataBodyRange.EntireRow.Delete
End If
'****************************************************************************************************************************************
'****************************************************************************************************************************************
'Escalations***********************************************************************************************************
'Set ThisWorkbook = Application.Workbooks("MPT_EndUser_revised.xlsx")
Set ws1 = MasterWB.Sheets("Escalations")
Set loEndUserTable = ws1.ListObjects("EscTracker")
Set rngIn = loEndUserTable.DataBodyRange
' only do it if there are rows in the table
If Not rngIn Is Nothing Then
Set ws2 = ThisWorkbook.Sheets("Escalations")
Set loMasterTable = ws2.ListObjects("EscTracker")
If loMasterTable.DataBodyRange Is Nothing Then
' if no rows yet added to master use the header range
Set rngOut = loMasterTable.HeaderRowRange
Else
Set rngOut = loMasterTable.DataBodyRange
End If
' move the range down to the first empty row in the master table,
' and resize it to be the same as the input range
Set rngOut = rngOut.Offset(rngOut.Rows.Count, 0). _
Resize(rngIn.Rows.Count, rngIn.Columns.Count)
rngIn.Copy
rngOut.PasteSpecial xlPasteValues
' now delete all rows from the input table
loEndUserTable.DataBodyRange.EntireRow.Delete
End If
'~~~~~~~~~SAVES Report Workbook, Exports to Access, and then Closes rawData workbook aka MasterWB ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
'~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
'~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
'saves source workbook info
ThisWorkbook.Save
'export newly retrieved data to access database
Call ExportToAccess
'save raw data workbook and close
MasterWB.Save
MasterWB.Close xlDoNotSaveChanges
With Application
.ScreenUpdating = True
.DisplayAlerts = True
End With
'Message Box to Inform End User update was successful
MsgBox "Thank You. Your DATA Transferred Successfully. You may now view the Roaming Backoffice Report."
End Function
My question is would I update the "progress bar" code to work with the vba shown above.
I downloaded the example workbook, read through your article and for an expert it explains it well but I'm sort of lost because of my inexperience with loops and setting MIN and MAX values for iterations. ((O_O))
Thank you in advance! :)
Hi abys757,
Your question is quite specific to your own situation and won't contribute to future readers, so what you should do is post a new question and reference this article and someone will assist you in exchange for points.
Your question is quite specific to your own situation and won't contribute to future readers, so what you should do is post a new question and reference this article and someone will assist you in exchange for points.
I've only seen this now. Seems very nice and will try to make it work for my tactical tools.
1 comment, 1 question.
Comment: instead of exporting and importing modules/forms you can simply drag and drop them from one workbook to the other.
Question on your procedure 'wasteTime'. You declare "Dim diag As New ProgressDialogue" but I get a compile error on this: "user-defined type not defined." Is there a reference I need to add?
1 comment, 1 question.
Comment: instead of exporting and importing modules/forms you can simply drag and drop them from one workbook to the other.
Question on your procedure 'wasteTime'. You declare "Dim diag As New ProgressDialogue" but I get a compile error on this: "user-defined type not defined." Is there a reference I need to add?
Featured Post
Prepare for the CompTIA Network+ exam by learning how to troubleshoot, configure, and manage both wired and wireless networks.
Join & Write a Comment Already a member? Login.
Suggested Articles
This Micro Tutorial will demonstrate the scrolling table in Microsoft Excel using the INDEX function.
Although Jacob Bernoulli (1654-1705) has been credited as the creator of "Binomial Distribution Table", Gottfried Leibniz (1646-1716) did his dissertation on the subject in 1666; Leibniz you may recall is the co-inventor of "Calculus" and beat Isaac…
