Calendar Problems moving from Access 2003 to 2010 (1 Viewer)

[KW99]

I wrote some databases a few years ago in Access 2003, however recently have upgraded to Access 2010.

Unfortunately I used the inbuilt calendars in Access, which following the upgrade to Access 2010 now no longer work (get a missing or broken ref to file mscalocx version 7).

I can obviously change all of the references to the new one in 2010, however would it be better to use a form based calendar (not an inbuilt one) so this does not happen in the future? Any thoughts or tips?

Does anyone have a good calendar to use as most of the ones I have found are pretty old?

Your thoughts and help would be much appreciated.

Thanks!

 

[vbaInet]

If you have converted from 2003 to 2010 then you will have to use the form based calendars. The calendar activex is not supported from Access 2007 onwards.

 

[missinglinq]

When converting from 2003 to 2007/2010, do fields defined as Date/Time have the same option of using the native, attached calendar as do apps originally created in 2007/2010?

 

[vbaInet]

Good question! Yes, the Show Date Picker property is still available if you were opening a 2003 db in 2007/2010 or converted a 2003 db to 2007/2010.

 

[missinglinq]

Thanks for the info! Haven't taken the plunge yet, but probably will, so trying to soak up all the post-2003 lore I can!

 

[vbaInet]

No problem! By the time you will get there you will be a fountain of knowledge. Well, seeing that you're a fountain of knowledge already it will be overflowing

 

[boblarson]

Does anyone have a good calendar to use as most of the ones I have found are pretty old?

I don't know what you consider "pretty old" but I've used this one in the past and you could format it up however you would like, with a little work.

 

[KW99]

Thanks for this.

I had looked at this one and I guess just wondered if there were some fancy ones out there now. Its no problem though I can customise as appropriate.

Does anyone know why Microsoft have abandoned the OCX Calendars from 2007 onwards?

I guess it will be better for 'future proofing' to have a form based one anyhow.

Thanks for the help

 

[missinglinq]

ActiveX Controls in general and ActiveX Calendars in particular have always been problematical in Access. You develop an app using a calendar in one version of Access and then upgrade to a newer version or distribute to a number of people running different versions and they bomb out because of different versions of Access have different versions of the controls.

This is why there are a number of form-based, non-ActiveX calendars out there. And 2007/2010 has the new functionality where a textbox bound to a Date/Time field has the ability to automatically popup a DatePicker to populate the given field, without any coding on the part of the developer.