[AccessD] Calendar Controls -- just for discussion

You're quite welcome.  As soon as life settles down, I'll finish up the new
version.  Which is keyboard friendly too!

Drew

-----Original Message-----
From: accessd-bounces at databaseadvisors.com
[mailto:accessd-bounces at databaseadvisors.com]On Behalf Of Andy Lacey
Sent: Sunday, April 18, 2004 5:01 PM
To: 'Access Developers discussion and problem solving'
Subject: RE: [AccessD] Calendar Controls -- just for discussion


> I use a modified version of Drew's old mini-calendar which is all VBA,
dead reliable, and very fast.
Ditto (and thanks to Drew)

-- Andy Lacey
http://www.minstersystems.co.uk 


> -----Original Message-----
> From: accessd-bounces at databaseadvisors.com 
> [mailto:accessd-bounces at databaseadvisors.com] On Behalf Of 
> William Hindman
> Sent: 18 April 2004 17:42
> To: Access Developers discussion and problem solving
> Subject: Re: [AccessD] Calendar Controls -- just for discussion
> 
> 
> ...first ...I don't use the ODE Calendar Control because of a 
> long history of versioning problems ...even when you wrap it 
> in a class you're app is still vulnerable ...besides it being 
> slow ...I use a modified version of Drew's old mini-calendar 
> which is all VBA, dead reliable, and very fast.
> 
> ...second (this has been discussed here recently but under 
> another thread
> topic) ...I much prefer data integrity over speed but its not 
> necessary to sacrifice one for the other ...I always force 
> user date entry from a pop-up calendar ...the calendar 
> pops-up at the bottom right of the text box with the current 
> date defaulted ...if the current date is what is required 
> ...a dblclick gets the date entered and tabs to the next 
> control ...if not, the cal responds to either mouse (slow) or 
> keyboard (fast) for date selection.
> 
> ...purists will try and tell you that such an approach slows 
> keyboarders down and they won't accept it ...I disagree 
> ...once the keyboarders get used to the keyboard strokes that 
> control the cal it is in most cases just as fast as them 
> entering it directly ...BUT ...big one ...the forced calendar 
> usage eliminates most date errors from users who enter/read 
> dates differently ...and the difference between error/dirty 
> data correction time and getting it right the first time 
> weighs heavily in favor of using a cal control over straight 
> user date entry.
> 
> William Hindman
> "Always code as if the person who is maintaining or testing 
> your code is a violent psychopath who knows where you live." 
> William Silverstein
> 
> 
> ----- Original Message ----- 
> From: "Susan Harkins" <ssharkins at bellsouth.net>
> To: "'Access Developers discussion and problem solving'" 
> <accessd at databaseadvisors.com>
> Sent: Sunday, April 18, 2004 11:44 AM
> Subject: [AccessD] Calendar Controls -- just for discussion
> 
> 
> > I'm writing about the ODE Calendar Control and I'm curious 
> how many of 
> > you use Calendar controls in your apps.
> >
> > I've had people complain about them -- they'd actually 
> enter the dates 
> > themselves because they find the break in their data entry routines
> annoying
> > -- from a data integrity point of view I can see the value of the 
> > controls
> > -- but how do you convince people to use them?
> >
> > Susan H.
> > --
> > _______________________________________________
> > AccessD mailing list
> > AccessD at databaseadvisors.com
> > http://databaseadvisors.com/mailman/listinfo/accessd
> > Website: http://www.databaseadvisors.com
> >
> 
> 
> -- 
> _______________________________________________
> AccessD mailing list
> AccessD at databaseadvisors.com
> http://databaseadvisors.com/mailman/listinfo/accessd
> Website: http://www.databaseadvisors.com
> 
> 

-- 
_______________________________________________
AccessD mailing list
AccessD at databaseadvisors.com
http://databaseadvisors.com/mailman/listinfo/accessd
Website: http://www.databaseadvisors.com