late binding of mscal.ocx calendar object

  • Thread starter Thread starter Guest
  • Start date Start date
G

Guest

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?
 
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

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