Home |
Search |
Today's Posts |
#1
![]()
Posted to microsoft.public.excel.programming
|
|||
|
|||
![]()
I have designed a complex Excel spreadsheet app in which I am not the end
user that uses heavy vba including a calendar control. It was designed with Excel 2003 and will be used on PCs with Excel 2003 and XP. I demonstrated the app on a PC in which everything worked fine, however when I saved it to the end user's PC it rejected the app because of a control not installed on the machine. Do we really have to do some preliminary installation on each PC using this app because of the calendar control? Shouldn't the control operate on any PC using the app? Sam |
#2
![]()
Posted to microsoft.public.excel.programming
|
|||
|
|||
![]()
Sam
The Caledar Control is mscal.ocx and is installed only if the version of MS Office used contains Access. You can download mscal.ocx from here. http://www.fontstuff.com/vba/vbatut07.htm Gord Dibben MS Excel MVP On Thu, 16 Aug 2007 18:10:27 -0700, Sam wrote: I have designed a complex Excel spreadsheet app in which I am not the end user that uses heavy vba including a calendar control. It was designed with Excel 2003 and will be used on PCs with Excel 2003 and XP. I demonstrated the app on a PC in which everything worked fine, however when I saved it to the end user's PC it rejected the app because of a control not installed on the machine. Do we really have to do some preliminary installation on each PC using this app because of the calendar control? Shouldn't the control operate on any PC using the app? Sam |
Reply |
Thread Tools | Search this Thread |
Display Modes | |
|
|
![]() |
||||
Thread | Forum | |||
Calendar Control | Excel Discussion (Misc queries) | |||
Calendar control | Excel Discussion (Misc queries) | |||
Control disappeared problem - specifically, the Calendar Control | Excel Programming | |||
calendar control | Excel Programming | |||
Calendar Control: Can't exit design mode because control can't be created | Excel Programming |