[AccessD] Calendar control

How about using Stephen Lebans Calendar control.
It is a wrapper around common control api calls so should be no 
versioning problem
http://www.lebans.com/monthcalendar.htm

Erwin Craps - IT Helps wrote:

>Yes indeed, but the control is connected to the office version.
>You can not use the A2K3 calendar control on a A2K machine, the A2K
>calendar control stays.. 
>
>I dont know how to check the calendar control version, but the access
>version must be simple.
>
>I'm looking at other controls like the Microsoft Date and Time picker...
>Looks nice to.
>
>Erwin
>
>
>-----Original Message-----
>From: accessd-bounces at databaseadvisors.com
>[mailto:accessd-bounces at databaseadvisors.com] On Behalf Of Gustav Brock
>Sent: Wednesday, April 13, 2005 1:09 PM
>To: accessd at databaseadvisors.com
>Subject: RE: [AccessD] Calendar control
>
>Hi Erwin
>
>Looks like a bug to me as vbSunday is 1 in all versions of Access.
>But it's a bug of the control not Access, so you should check the
>version of the control (or rather the reference to the control), not of
>Access.
>
>/gustav
>
>
>  
>
>>>>Erwin.Craps at ithelps.be 04/13 12:52 pm >>>
>>>>        
>>>>
>I believe I explained myself poorly...
>
>The issue is that Calendar control of A2K has 1 (vbSunday) for Sunday.
>The calendar control of A2K3 has 1 (vbSunday) for Monday.
>So the calendar control of A2K3 already use the system local firstday.
>
>But thats the problem...
>If I set the calendarcontrol of A2K3 firstday property to 1 I get Monday
>as the first day.
>If I move that database to a A2K pc, the calender control will display
>Sunday as the first day.
>Because In VBA Sunday should always be the first day (vbSunday Contant).
>
>So probably the only soluation is to check which version of
>calendarcontrol or Access is running and set the firstday to 1 or 2
>according to the access version.
>
>Or not using the calendar control :-(
>
>Erwin
> 
>
>-----Original Message-----
>From: accessd-bounces at databaseadvisors.com
>[mailto:accessd-bounces at databaseadvisors.com] On Behalf Of Gustav Brock
>Sent: Tuesday, April 12, 2005 5:56 PM
>To: accessd at databaseadvisors.com
>Subject: RE: [AccessD] Calendar control
>
>Hi Erwin
>
>A clue is here:
>
>  http://www.vb-helper.com/howto_set_calendar_first_weekday.html 
>
>/gustav
>
>  
>
>>>>Erwin.Craps at ithelps.be 04/12 5:27 pm >>>
>>>>        
>>>>
>Ok, this seems like a bug to me.
>
>The A2K calendar control give for Monday as the firstday, the A2K3
>calendar control gives Tuesday as the firstday when having the property
>.FirstDay set to vbMonday (2)
>
>Fun fun fun
>
>Anyone knows how I can get the Windows system firstday?
>
>Erwin
> 
>
>-----Original Message-----
>From: accessd-bounces at databaseadvisors.com
>[mailto:accessd-bounces at databaseadvisors.com] On Behalf Of Erwin Craps
>-
>IT Helps
>Sent: Tuesday, April 12, 2005 5:05 PM
>To: Access Developers discussion and problem solving
>Subject: [AccessD] Calendar control
>
>Is there a bug in the calendar control of MSA2K3?
> 
>When using a MDB file in A2K3 my firstday is monday.
>When using this MDB file on a A2K computer the firstday is sunday and
>the dates are so small they look like a dot.
>It seems that the font is set to 1.5 instead of 8.25.
> 
>So in an attempt to solve this I VBA code my fonts to 8.25 and my
>firstday to vbMonday.
>Should be right?
> 
>No way, When looking to my calendarcontrol in MSA2K3 the firstday is
>tuesday!!!
>I supose it will be good in A2K, but how am I to work around this one?
>
>--
>AccessD mailing list
>AccessD at databaseadvisors.com
>http://databaseadvisors.com/mailman/listinfo/accessd
>Website: http://www.databaseadvisors.com
>  
>

-- 
Marty Connelly
Victoria, B.C.
Canada