Drivewindow Light 2.94 Official
On this page I show how to make a calendar and date picker on an Excel userform using VBA only and no ActiveX.
This is how it looks in the Danish version of Excel 2003:
In the U.S.A (English), where the first day of the week is Sunday and not Monday, the "day labels" from left to right will be SU, MO, TU, WE, TH, FR and SA, and February 1st 2016 will be in the second column, below MO.
In other words it is sensitive to the system's language and first day of the week settings. The possible date formats are also based on the system settings.
By using VBA only and no ActiveX you avoid compatibility problems, because different MS Office versions use different ActiveX controls for calendars.
You can use the calendar to select (up to) two dates for whatever purpose you want. The selected dates are put in two labels, and if you click one of these labels, you can copy the date to a cell or a range of cells.
I show and explain some of the macros below, but I cannot show them all. If you want to see the rest, you can download a zip compressed workbook with the example.
The workbook was updated with a minor bug fix February 26th 2017.
The calendar is on a userform (see image above) with a frame, labels, combo boxes and command buttons.
For event handling (when the user selects a date) the calendar uses a simple class module instead of writing a click procedure for each and every date label.
Of course it also uses quite a few date functions like getting the first day of the week, first day of the month, weekday names in the user's language, checking for leap year etc.
I am a lousy designer, so change the userform's look as you like; but unless you change the code, the labels for date picking must all be in Frame1.
The Collections
There are two public collections declared in Module1: colLabelEvent and colLabels, and the calendar's date labels are members of both collections.
colLabelEvent is a collection of the event handler classes for the labels, and colLabels enables us to change the properties of each label like e.g.:
colLabels.Item(variable for label name).Visible = False
We'll get back to the event handling class - it is really not complicated.
The userform's Initialize procedure
A userform's Initialize procedure executes before the form opens, and below you can see how it looks in the calendar userform.
However, like all software tied to specific hardware generations, Drivewindow Light 2.94 exists within a lifecycle. As ABB transitions to newer platforms like Drivewindow Classic or web-based interfaces integrated into the drives themselves, reliance on specific legacy versions like 2.94 may diminish. Yet, for the installed base of drives currently in operation globally, this software remains a vital maintenance tool. Its stability and specific feature set make it a reliable workhorse for facilities that prioritize continuity over constant upgrade cycles.
Furthermore, a key feature of this software version is its real-time diagnostic capability. Industrial environments are dynamic, and motors are subject to fluctuating loads and potential faults. Drivewindow Light 2.94 facilitates real-time monitoring of drive status, allowing the operator to visualize actual signals—such as motor speed, current, and torque—as they happen. This "window" into the drive's operation is invaluable for troubleshooting. For instance, if a motor is tripping unexpectedly, the engineer can use the software to view the fault logger, which provides a timestamped history of events leading up to the failure. The specific iteration of 2.94 would have focused on compatibility with newer Windows operating systems of its time, bridging the gap between older hardware interfaces and modern computing standards.
Version 2.94 is designed to run on modern Windows environments (up to Windows 10/11 with compatibility settings).
The tool allows for one-click backups. If a drive fails, you can clone its entire personality onto a new unit in minutes.
The Initialize procedure ended by calling the LabelCaptions procedure passing two arguments, namely the present month and year.
The LabelCaptions procedure does several things that determine the look of the calendar, and it is called every time the user changes month or year.
It checks stuff like the number of days in the month, where to put the first date according to the first day of the week, it finds the first day of the month and more. Here is how it looks:
Drivewindow Light 2.94 Official
However, like all software tied to specific hardware generations, Drivewindow Light 2.94 exists within a lifecycle. As ABB transitions to newer platforms like Drivewindow Classic or web-based interfaces integrated into the drives themselves, reliance on specific legacy versions like 2.94 may diminish. Yet, for the installed base of drives currently in operation globally, this software remains a vital maintenance tool. Its stability and specific feature set make it a reliable workhorse for facilities that prioritize continuity over constant upgrade cycles.
Furthermore, a key feature of this software version is its real-time diagnostic capability. Industrial environments are dynamic, and motors are subject to fluctuating loads and potential faults. Drivewindow Light 2.94 facilitates real-time monitoring of drive status, allowing the operator to visualize actual signals—such as motor speed, current, and torque—as they happen. This "window" into the drive's operation is invaluable for troubleshooting. For instance, if a motor is tripping unexpectedly, the engineer can use the software to view the fault logger, which provides a timestamped history of events leading up to the failure. The specific iteration of 2.94 would have focused on compatibility with newer Windows operating systems of its time, bridging the gap between older hardware interfaces and modern computing standards. drivewindow light 2.94
Version 2.94 is designed to run on modern Windows environments (up to Windows 10/11 with compatibility settings). However, like all software tied to specific hardware
The tool allows for one-click backups. If a drive fails, you can clone its entire personality onto a new unit in minutes. Its stability and specific feature set make it
Below is the function that finds the number of days in the selected month. It is quite simple.
Function DaysInMonth(lMonth As Long, lYear As Long) As Long
Select Case lMonth
Case 1, 3, 5, 7, 8, 10, 12
DaysInMonth = 31
Case 2
If IsDate("29/2/" & lYear) = False Then
DaysInMonth = 28
Else
DaysInMonth = 29
End If
Case Else
DaysInMonth = 30
End Select
End Function
There are more procedures handling user actions like changing month or year using the month or year combo boxes. That is more or less trivial stuff, and you can see the code, if you download the workbook.
The most important thing left is the label event handling class.
The event handling class
In the userform's Initialize procedure we connected all the date labels to the class clLabelClass and put them in a collection, colLabelEvent.
The user picks a date by clicking a date label, and if you didn't have the class handling this event, you would have to write a click procedure for each end every label. Now all clicks are handled by the class module code below.
The code uses some Public variables like sActiveDay declared im Module1.
Option Explicit
Public WithEvents InputLabel As MSForms.Label
Private Sub InputLabel_click()
With InputLabel
If .Tag < lStartPos Then
If UserForm1.lblBack.Enabled = True Then
UserForm1.lblBack_Click
End If
Exit Sub
End If
If .Tag > lDays + lStartPos - 1 Then
UserForm1.lblForward_Click
Exit Sub
End If
If .BorderColor = vbBlue Then Exit Sub
.BorderColor = vbBlue
.BorderStyle = fmBorderStyleSingle
If Len(sActiveDay) > 0 Then
If sActiveDay <> InputLabel.Name Then
With colLabels.Item(sActiveDay)
.BorderColor = &H8000000E
.BorderStyle = fmBorderStyleNone
End With
End If
End If
sActiveDay = InputLabel.Name
lFirstDay = Val(InputLabel.Caption)
If bSecondDate = False Then
UserForm1.FillFirstDay
Else
UserForm1.FillSecondDay
End If
End With
End Sub
That was the most important parts of the calendar's code. To see the rest, download the workbook.
The selected date or dates will be in two labels on the user form, but internally they are stored in the variables datFirstDay and datLastDay (declared on module level in the userform).
A date or dates can be used in many ways, and you can put your own code in the OK button's click procedure.
As sample code I find the difference in days between the two dates and display it in a message box, before the form closes. You can just replace that with your own code.
By picking my birthday and the day I write this, I can see, that I have lived for 21979 days. Time sure flies ...
Related:
|