Alyson
Loose the Active X Calendar control.
My Previous experience with Access and Active X controls has led me to
create the following rule. "Thou shall not use any widget in an Access
application that did not ship with Access or is not part of the operating
system of Win 98 or higher". I have not been burnt since!!! Let's face it
Access is not a friendly environment for many Active X controls. Most Access
applications are not deployed using a full blown windows installer program
that could make sure all of the components that re needed get installed.
I have found 2 possible solutions that meet my criteria for non Active X
widgets. Stephen Lebans API generated calendar
(http://www.lebans.com/monthcalendar.htm), and Allen Browns 100% Access only
solution (http://allenbrowne.com/ser-51.html). While Stephens solution is
brilliant, flexible, and comprehensive. It is also complex and way overkill
for a software minimalist like myself. Allen Browns Calendar that is
equally brilliant, small, native to Access with no dependencies, and
seemingly "unbreakable".
Either will work anywhere Access and Windows works, requiring no additional
files to install, no changes to the registry to fret over, Zero versioning
problems (which I suspect is your problem), and fewer grey hairs for the
developer.
Ron W
> I have a calendar control on a form that is used for a date field by double
> clicking in the field - it works fine in 50% of the machines that the
[quoted text clipped - 5 lines]
> anyone know the best settings for a machine to stop this from happening?
> Thanks for your help
Alyson D - 15 Jul 2005 20:02 GMT
Ron - thanks for the input - I will implement your idea
Alyson
>Alyson
>
[quoted text clipped - 29 lines]
>> anyone know the best settings for a machine to stop this from happening?
>> Thanks for your help