Hi everyone,
My question is about an ActiveX Visual Basic Calendar control that I am using in an MIS system that I have developped. The system works fine in Excel 97 but when I tried to install it in Excel 2000 I get an error "This feature is not available on this computer". When I go to the VB editor, and try to get help for the feature (VBCalendar control) it prompts me to load 'data.msi' from the Office 2000 CD. After loading the file, it didn't work right away. I had to dump the calendar control into the System32 folder for VB to reference it. VB then showed the reference but it still wasn't working. I moved the file around from folder to folder and restarted the computer until it finally worked for some miraculous reason.
I tried to install it on another computer with Office 2000 and I got a similar error. I placed the VBCalendar control in the system32 folder and then that worked ... or so I thought. Again I had to move the file around from folder to folder until the calendar showed up. However, when I try to use the calendar I get an error "ActiveX object cannot be created"
My question is: What the hell?
What did Office 2000 load?
Why didn't VB pick up the reference right away after the VBCalendar was placed in the system32 folder?
What is really missing in Office 2000 that needs to be loaded for this feature to work?
What is up with the ActiveX object error?
How do ActiveX controls fit in to all of this?
Why is this simple little calendar causing so many problems?
Your helpful tips would be greatly appreciated.
SLY
My question is about an ActiveX Visual Basic Calendar control that I am using in an MIS system that I have developped. The system works fine in Excel 97 but when I tried to install it in Excel 2000 I get an error "This feature is not available on this computer". When I go to the VB editor, and try to get help for the feature (VBCalendar control) it prompts me to load 'data.msi' from the Office 2000 CD. After loading the file, it didn't work right away. I had to dump the calendar control into the System32 folder for VB to reference it. VB then showed the reference but it still wasn't working. I moved the file around from folder to folder and restarted the computer until it finally worked for some miraculous reason.
I tried to install it on another computer with Office 2000 and I got a similar error. I placed the VBCalendar control in the system32 folder and then that worked ... or so I thought. Again I had to move the file around from folder to folder until the calendar showed up. However, when I try to use the calendar I get an error "ActiveX object cannot be created"
My question is: What the hell?
What did Office 2000 load?
Why didn't VB pick up the reference right away after the VBCalendar was placed in the system32 folder?
What is really missing in Office 2000 that needs to be loaded for this feature to work?
What is up with the ActiveX object error?
How do ActiveX controls fit in to all of this?
Why is this simple little calendar causing so many problems?
Your helpful tips would be greatly appreciated.
SLY