MS 2010 Calendar control missing and buttons show as checkboxes 1

[1DMF]

Hi,

I've just created an MDE with my Access 2003 application, however a user with a new machine and Access 2010 doesn't seem to be able to use it?

All calendar controls 'MSCAL.Calendar.7', are missing and even buttons are showing as check boxes?

I did a quick Google and read that MS 2010 was deprecating the calendar OCX all together , is this correct and if so what can i do to fix my app for this user?

And why are some buttons showing a check boxes?

Thanks,
1DMF

"In complete darkness we are all the same, only our knowledge and wisdom separates us, don't let your eyes deceive you."

"If a shortcut was meant to be easy, it wouldn't be a shortcut, it would be the way!"

Google Rank Extractor -> Perl beta with FusionCharts

 

[Golom]

MSDN gives some suggestions for controls that can be used to replace MSCAL.OCX here

As to the check boxes, that can be an indication that the control you are using can no longer be found and the system "helps you out" by substituting some other control. It usually substitutes a picture box but a checkbox is also a possibility.

Are the controls that appear as checkboxes really standatd buttons?

 

[MajP]

http://www.granite.ab.ca/access/calendars.htm

Here are a few homegrown ones using access forms or the windows API.

 

[MajP]

I also have used this one for a long time.

http://allenbrowne.com/ser-51.html

 

[1DMF]

I'm a bit confused, it says use date picker, where is date picker in Access 2003?

I had a closer look at the controls, although on first impression they look like check boxes, it's just the way they have been rendered, it seems it is a button but it cannot fit the text on it, and the white with shadow made them look like checkboxes.

What property is causing this behaviour?

This date calendar issue, is going to cost me at least a week if not more of re-writing exisiting applications because of MS.

I guess the moral of the story is never use an MS calendar in any of your applications ever, because they cannot be trusted to keep them in later versions and your entire application will stop functioning where ever the calendar is used.

I mean who wants to type dates into text boxes these days, or have to validate the input to the correct date format, that's the point of a calendar control!

The boss is not going to be a happy bunny, his schedule has just been put way back!

"In complete darkness we are all the same, only our knowledge and wisdom separates us, don't let your eyes deceive you."

"If a shortcut was meant to be easy, it wouldn't be a shortcut, it would be the way!"

Google Rank Extractor -> Perl beta with FusionCharts

 

[1DMF]

MajP, I'm using the allen browne one, shame it requires two clicks to select a date (have to press OK as well as desired date), but apart from that looks OK.

One thing I noticed, many of the funtions have error handling code, yet all the 'OnError' keywords have been commented out?

Any reason for this? If the error handling has been removed, isn't this just code bloat?

I've uncommented all the OnError commands, but your advice is appreciated.

"In complete darkness we are all the same, only our knowledge and wisdom separates us, don't let your eyes deceive you."

"If a shortcut was meant to be easy, it wouldn't be a shortcut, it would be the way!"

Google Rank Extractor -> Perl beta with FusionCharts

 

[MajP]

Never noticed. I will take a look. My guess it is just leftover, maybe he centralized the error trapping in his original code.