D
david anon
MSCAL.OCX calendar control works fine on my desktop PC -
it is reused on a pop-up form to populate dates throughout
the application.
When packaged & installed to other PCs, the form crashes
the runtime. Deleting the ocx from the client PC stops
this very simple form from crashing the PC - but obviously
the app. doesn't work without it.
Any ideas about how to fix this?
Form has a calendar and an OK button, nothing more. The
calendar control is unbound, and the code behind the form
is dead simple:-
Private Sub cmdOK_Click()
If Not (IsDate(Me.Calendar1)) Then Me.Calendar1 = Date
Me.Visible = False
End Sub
it is reused on a pop-up form to populate dates throughout
the application.
When packaged & installed to other PCs, the form crashes
the runtime. Deleting the ocx from the client PC stops
this very simple form from crashing the PC - but obviously
the app. doesn't work without it.
Any ideas about how to fix this?
Form has a calendar and an OK button, nothing more. The
calendar control is unbound, and the code behind the form
is dead simple:-
Private Sub cmdOK_Click()
If Not (IsDate(Me.Calendar1)) Then Me.Calendar1 = Date
Me.Visible = False
End Sub