ACCESS 2013 Date Picker Issue - Run-time error '2683' 1

[evil1966]

I have a database that was programmed a decade ago. It has been upgraded several times for various editions of MS Access. Now I've had to move everyone to Office 2013 Pro and I copied the MsCal.ocx over and pointed correctly so that the database opens correctly.

Now the issue is whenever someone double clicks on a date field to bring up the date picker it throws the Run-time error '2683' There is no object control.

Is there a fix for this or do I have to bring back the programmer?

Thanks!

 

[dhookom]

Why don't you use the date picker available in Access? If the format is set to a date format, the date picker should appear in the got focus of the text box.

Duane
Hook'D on Access
MS Access MVP

 

[MajP]

http://msdn.microsoft.com/en-us/library/gg251104(v=office.14).aspx

 

[evil1966]

MajP,

I'm looking at that link right now. I'll have to read it in detail, but it looks like this is the solution. I'm hoping I don't have to try to go through the entire database to reset every date field. I did copy MSCAL.OCX into the users files C:\Program Files\Microsoft Office\Office15 and pointed their VB objects to it. Without doing that much the database wouldn't run at all.

Thanks!

 

[strongm]

>I did copy MSCAL.OCX

Which you are technically not allowed to do under the terms of the license. MSCAL.OCX is not redistributable, unfortunately. Which is one of the reasons the article MajP linked states "you must remove each instance of the control

 

[wvmitchell]

If you don't like the built-in date picker, take a look at the Ken Getz "Access 97 Developer's Handbook" which can be found on Amazon for less than $20 USD... Chapter 8 has a pop-up Calendar form that does not require ActiveX.

BTW you can redistribute the MSCAL.OCX, however you need to have a license for the Access Developer Edition.

 

[evil1966]

Thanks, wvmitchell. I'll look into that.