Fabian I do not have this entire thread on my server but did the
original post ask for a 64 bit Web based solution? What version of
Access is 64bit?
It looks like they simply want a Calendar control to work on a Tab
control on an Access Form. If that's the case then the MonthCalendar
solution on my Web site will work for them.
The only reasons I produced this non ActiveX solution are:
1) DLL hell encountered by developers distributing the Calendar OCX.
2) Request for the ability for the users to change the Calendar props at
runtime to their own personal preferences.
3) Support for the DayState property.
Access Code, Tips and Tricks
Please respond only to the newsgroups so everyone can benefit.
> This almost certainly won't work on a 64bit environment (unlike
> controls). API based solutions are not as OS independant as ActiveX -
> evident via the fact that ActiveX is used for the Web while API's are
> used (except for server side stuff where the OS is known).
> > I've just found a control that uses API calls (ie is not an ActiveX
> > that may be useful. I haven't tried it and it may not be perfect
> > job, but it may solve a lot of your's and my problems.
> > The web site is: http://www.lebans.com/monthcalendar.htm
> > Darren.
> > > Darren, what would you use instead? Jaci
> > > > Andre,
> > > > I've used the MS DateTime Picker controls on the Tab Control in
> > 97.
> > > > I've got them to work, but I've had heaps of problems.
> > > > I'm not sure that I've had your particular problem but I found
> > > > can't copy and paste the DateTime Picker control. There seems
> > some
> > > > kind of internal referencing that doesn't get updated when the
> > is
> > > > copied. To work around this you have to select the ActiveX from
> > > > annoyingly slow "More Controls" list on the Toolbox every time
> > to
> > > > place the control on a form (or tab).
> > > > Also I haven't bound any of my DatePicker Controls to any
> > the
> > > > value into the controls as appropriate.
> > > > I've had quite a few other problems, so I would suggest that, if
> > possible,
> > > > you avoid the DateTime Picker control (in fact most if not all
> > > > controls) in MS Access.
> > > > Darren.
> > > > > I forgot to mention that all controls have a controlsource and
> > binded
> > > > to
> > > > > a table.
> > > > > Andr
> > > > > > Hi.
> > > > > > It seems that the activeX control DateTime Picker doesn't
> > Tab
> > > > > > Control.
> > > > > > I have a form with 11 pages. There is a DateTime Picker
> > each
> > > > > > page.
> > > > > > I am getting an error for each control that is not shown on
> > current
> > > > > page
> > > > > > when I load the form.
> > > > > > The error is "An error occured in a call to the Windows Date
> > Time
> > > > > Picker
> > > > > > control.".
> > > > > > Did somebody encouter that error before ?
> > > > > > Andr Deshaies
> > > > > > Montral