Daniel,
Follow-up question:
I looked at Allen and Stephen's calendars, but I'm going to really miss the
simplicity of what I have and anticipate many, many hours trying to adapt
one of theirs to look and function like what I already have. I don't need or
want a popup calendar, or one that sets the value of a text box -- just a
calendar that's already open and part of the main form that I open and which
has a number of other controls on it. For example, the type of service that
was provided, the staff person providing that service, etc. Together with
this other information, the user clicks a date on the calendar and then
other command buttons/procedures can refer to the calendar control for the
date value. (Hope this makes sense).
Anyhow, just wondering if there's a reference in Access 2010 that I could
set, or some other techniques, that would allow me to still use what I
already have?
Thanks,
Mark
"Daniel Pineault" <(E-Mail Removed)> wrote in
message news:B6D26CAA-E2B3-4B10-B6B4-(E-Mail Removed)...
> The situation you are describing is the exact reason why using calendar
> controls which are dependant on ocx, dll,... are a bad idea as you then
are
> faced with versioning issues.
>
> The only way around this is to implement a calendar which does not rely on
> said references... a calendar such as Allen Browne or Stephen Lebans.
They
> are both easy to implement (1-2 minutes) and very, very reliable!!! They
> work (in my experience) in Access 2000, 2003, 2007. For more information
see:
>
> http://www.devhut.net/index.php?lang...00004#datepick
> --
> Hope this helps,
>
> Daniel Pineault
> http://www.cardaconsultants.com/
> For Access Tips and Examples: http://www.devhut.net
> Please rate this post using the vote buttons if it was helpful.
>
>
>
> "Mark" wrote:
>
> > Hi all,
> >
> > I still do most of my development at home using Access97. At work, I
convert
> > the FE to the default 2000 format on a computer running Access 2002(or
maybe
> > it's 2003, I'm not sure which). I can then distribute that converted FE
to
> > either Access 2002/2003 and Access 2007 computers and everything works
fine.
> >
> > Someone showed up with Access 2010 and the Calendar Control that I use
> > (MSCAL.Calendar.7 on the Access97 computer) produces a "cannot open
object"
> > (or similar) error message when I try to open the form that contains
that
> > control. I've not run into other problems on the 2010 computer (but,
> > admittedly haven't checked everything out). References appear OK.
> >
> > Would it make a difference, do you think, if I converted from 97 to
> > 2002/2003, instead of 2000, and then ran the FE under 2010? I haven't
had a
> > chance to try that yet, but thought someone might already know what
needs to
> > be done (other than upgrading my Access at home <g>).
> >
> > Thanks for any leads.
> > Mark
> >
> >
> > .
> >
Similar Threads
