Calendar Control 11.0

[skydiver]

Access 2003. How can I get a calendar that displays the current date when the form is opened?

 

[vbaInet]

On the Load event of the form:

Me.CalendarControlName.Value = Date

 

[skydiver]

vbaInet,

Let me elaborate a bit more. Currently on my form (Switchboard), on load I have:

Private Sub Form_Load()

DoCmd.Maximize

End Sub

Shall I include the calendar code within the "Private Sub Form_Load() procedure?

 

[vbaInet]

Shall I include the calendar code within the "Private Sub Form_Load() procedure?

Correct! Before or after DoCmd.Maximize

 

[skydiver]

Not working. The calendar still appears on the date I created it.

 

[vbaInet]

Did you close and save the form before running it?

 

[skydiver]

Yes. I even tried doing before and after. No luck.

 

[vbaInet]

Let me see your db.

 

[missinglinq]

You do realize that you have to replace CalendarControlName in vbaInet's code with the actual name of your calendar, right?

 

[skydiver]

Missinglinq,

Good eye...I had changed it to my calendar name, but no-go. Thanks though!

 

[skydiver]

vbaInet,

How can I get you my database?

 

[vbaInet]

vbaInet,

How can I get you my database?

http://www.access-programmers.co.uk/forums/showthread.php?t=140587

By the way, you didn't set the Control Source of the calendar control did you?

 

[skydiver]

Here ya go.

 

[boblarson]

Okay, figured it out. You need to change the Switchboard form's ALLOW EDITS property to YES.

 

[skydiver]

Bingo! Thanks Bob! I owe you a coke!!!

 

[missinglinq]

Very good, Bob, but how odd!

With a form's AllowEdits Property set to No you can set non-ActiveX controls values using code.

As John Walton used to say "Life's a mystery!" At least where Access is concerned!

Linq ;0)>

 

[boblarson]

Very good, Bob, but how odd!

With a form's AllowEdits Property set to No you can set non-ActiveX controls values using code.

As John Walton used to say "Life's a mystery!" At least where Access is concerned!

Linq ;0)>

Perhaps it is because essentially you are modifying the control (albeit setting a property) and Access can't manage that if it is something from outside the normal Access controls.

 

[missinglinq]

Maybe so. ActiveX controls, especially calendars, have always been problematical, of course.

 

[boblarson]

Maybe so. ActiveX controls, especially calendars, have always been problematical, of course.

And why I avoid using them unless it is absolutely, positively necessary to accomplish what I need to accomplish. I use a form based calendar instead of an ActiveX control as well because of the issues.

And skydiver -

You may want to rethink using it because that calendar control is now now longer available within Access (in 2010) and will cause an error if you have one if, and when, your company upgrades.