Level Extreme platform
Subscription
Corporate profile
Products & Services
Support
Legal
Français
Using the Microsoft MonthView Active X Control
Message
General information
Forum:
Visual FoxPro
Category:
The Mere Mortals Framework
Miscellaneous
Thread ID:
00254729
Message ID:
00255020
Views:
19
Yep, but that isn't actually my problem. I'm not really having a problem with using the GetDayBold. Every time I try to navigate outside of the current month, I get an error from GetDayBold of type mismatch. I don't have any code in the GetDayBold, so this is just native to the control.

I understand that the control will call the GetDayBold after navigating to a different month so that it can retrieve which days are supposed to be bold.

Here's what I know: If I use a form class based on the framework, it will crash. If I use just a form (not a form class), it doesn't crash. However, this isn't really what I want, since I would like to inherit the features of the framework base form. For example, I would like it to save and restore the screen position for the form.

It seems to have something to do with code or properties of the base form class, but I am unsure.

Anyone have any input? Kevin, if you are reading, do you have any ideas?

TIA

>Doug,
>As your luck would have it, I got off the phone with VFP tech support
>today on a similar issue. The problem I had was with the daybold property.
>It turns out that this control has problems with VFP and doesn't convert
>types properly. For example, the following code from the help file
>will not work with VFP:
>form1.olecontrol1.daybold(form1.olecontrol1.visibledays(1)) = .t.
>
>the workaround is
>form1.olecontrol1.object.daybold(ttoc(datetime())) = .t.
>
>Be sure to use the ttoc() function for all dates passed to the control (this is not documented anywhere), and use the .object.property syntax of the control.
>
>HTH
>Ed
>
>
>Hi All,
>>
>>Anyone run into this problem:
>>
>>I am trying to use the Microsoft MonthView control (version 6), and I am having a problem where I get an OLE Error blah blah, which essentially means that there is a type mismatch. Everything points to the GetDayBold event. Here's the catch:
>>
>>If I use a form (not a form class), I don't get the error, but if I use a form class, I get the error. Also, if I use a form class not based on the framework outside of my application, I don't get the error.

Doug Stalter

"According to the proverb, the best things are the most difficult." -Plutarch
Previous
Reply
Map
View

Click here to load this message in the networking platform