late binding of mscal.ocx calendar object

Thread view:

Enable EMail Alerts

Start New Thread

Thread rating:

Doug - 18 Oct 2007 12:28 GMT

I have an Access 2002 application that uses this control. I am having issues
with client machines having different versions of the file causing the #Name
issue. I would like to try late binding of the object to get around this.
Does someone have an example of the VBA code required to do this?

Reply to this Message

Allen Browne - 18 Oct 2007 12:39 GMT

Is the OCX worth the trouble?

How about using a little Access form like this:
http://allenbrowne.com/ser-51.html

Alternatively:
http://www.lebans.com/monthcalendar.htm

Signature

Allen Browne - Microsoft MVP. Perth, Western Australia
Tips for Access users - http://allenbrowne.com/tips.html
Reply to group, rather than allenbrowne at mvps dot org.

>I have an Access 2002 application that uses this control. I am having
>issues
> with client machines having different versions of the file causing the
> #Name
> issue. I would like to try late binding of the object to get around this.
> Does someone have an example of the VBA code required to do this?

Reply to this Message

Alex Dybenko - 19 Oct 2007 08:35 GMT

Hi,
you can't have activex control late bound, so you have to install same
version on all PCs, or follow Allen advise

BTW - never have version compatibility problems with calendar control, using
it in all my apps. Perhaps something else causing this error

Signature

Best regards,
___________
Alex Dybenko (MVP)
http://accessblog.net
http://www.PointLtd.com

Reply to this Message