Actually, I am kind of surprised they call this a bug.
Most controls do NOT update until you move the focus to the next control.
So, if you type in a new value into the company field, the value does NOT
change until you move to a new control. Hardly really a bug...and since it
worked this was for the last 3 versions....it is rather on the nice side
that it is still being called a bug.
The worked suggested however is one that I DO NOT like!
I would consider using un-bound calendar controls. In the forms on-load, I
would set the value of each calendar
me.ActMyCalStart.Value = me.StartDate
me.ActMyCalEnd.Value = me.EndDate
I would then use the after update event of the calender to set the field
value you want. Note that just like when developing in VB, the events list
is NOT available. So, while looking at the event tab of the calendar
control, you will notice that the after update event IS NOT available.
However, if you open the code window, and type in the event code...it will
work. So, use the after update event like
Private Sub ActiveXCtl14_AfterUpdate()
Me.StartDate = Me.ActiveXCtl14.Value
end sub
Or, as my example,...it would be:
Private Sub ActMyCalStart_AfterUpdate()
Me.StartDate = Me.ActMyCalStart.Value
end sub.
So, use the correct/same name you used for the control. Further, ALWAYS use
the .value property of the calendar control, since if you don't...I seen
some problems. So, always use the .value.
In most of my code examples, I actually don't place the calendar on the
form, but "pop" up a calendar. That way, I only have ONE calendar that can
service all fields. However, for things like report screens etc, the
calendar is a great little tool. Here is some screen shots of me using the
calendar...and all of the examples use the after update event. Also, all of
the example calendar are actually a sub form, as once again I only wanted
ONE copy of the calendar in the whole project.
http://www.attcanada.net/~kallal.msn/ridesrpt/ridesrpt.html