Strange problem with MS Access 2010 Date Picker

[jonathanchye]

Hi all,

I have a VERY weird problem with the MS Access 2010 date picker that I hope someone could point out to me what I did wrong. I have a main form with a subform in Datasheet view. The problem occurs in a Date field in the subform.

In normal circumstances the date picker seems to work fine but sometimes when I open form to add new records nothing happens when I select a date in the date picker. I've tried every process I can to eliminate this problem but I can't seem to find an absolute answer. It just happens when I use the form "as intended" but doesn't seem to happen when I go into Design Mode and back etc and this really adds to the frustration...

Can anyone think of why nothing appears when you select values in the MS2010 date picker?

edit: I would like to add it is fine if I manually type in the date though... I also have Data Validation active on these "cells" but I don't think that should matter? I also have an After Update check but when I go into Design Mode and back it seems to work fine! It's just when I open the form from my main menu this doesn't work... Frustrating!

Cheers...

 

[jmaty23]

I am having the same exact issue. Anyone have any thoughts?

 

[Pat Hartman]

Check the form properties on the data tab to ensure that the AllowEdits is set to yes. Also check the control properties on the data tab to ensure that the control is enabled and not locked.

 

[jmaty23]

I copied the form, query and table to a different computer and the problem stopped. Both are running Win 7 with Access 2010. Not sure why it works on one and not the other.

 

[jdraw]

Check the attached jpg. It shows a property that may be set
-For Dates
-Never

It may be set differently on different machines.

 

[jmaty23]

This is something that I checked a few times when it was happening. Its set to "For Dates" on all Date fields.

 

[jdraw]

I did some work with a poster who was converting some earlier Access applications to 2010 and need to "turn off the date picker".
Here is a link to the thread.
http://www.access-programmers.co.uk/forums/showthread.php?t=241240

There may be something in our posts that is of use to you.
Good luck

 

[jonathanchye]

Argh! Have this issue again. It was working fine and just stopped working out of the blue! Once the date picker stop working it won't work again

One thing I've noticed that the problem is only when the date picker is in a subform. I've opened the subform on it's own and the date picker populates the date correctly but it won't work when the subform is opened from the parent form ... strange.

 

[jonathanchye]

I find that this problem can be regularly replicated for Datasheet forms and if the bound control has an After Update event attached.

If the bound control has no even attached the Date Picker works! Frustrating...

 

[raul_vargas_pr]

I had the same problem and was able to fix it by simply deleting the input mask for the date on the table level and in the form. Hope it works for you.

 

[speakers_86]

I'm seeing this issue too. There is no after update event nor a mask.

 

[speakers_86]

So I narrowed it down. I commented all of the form's code and the issue disappeared. I narrowed it further to my resize event. There is a block that sets the column order of all the controls that is causing it. I can't tell why, maybe just corruption.

 

[speakers_86]

Thanks to this post I got a work around:
https://bytes.com/topic/access/answers/942767-calendar-not-working

After the offending code runs, I am setting the focus to the control with the date picker. That's it! I guess it's just some weird glitch in the picker itself. Hopefully this helps the op.

 

[The_Doc_Man]

I have found it useful to do something in the Form_Current routine to test whether a date field is null/empty/0/blank. The date-picker control seems to work better if you check that there is actually a date in the control (from the underlying record). In my case, however, the form was unbound - so what I did was that if the conditions for pre-loading the date with something "real" weren't met, I loaded Now() to the date field.

It seems that if the picker doesn't see something in an unbound field that looks like it COULD be a date, the picker value "For Dates" isn't being met correctly.

 

[dbwhiz2006]

I registered for this forum just so I could say Thank U. I've been doing this for 25 years, have 30 or so different apps in production, and suddenly the date picker for a field on a subform wouldn't plug the date into the field once u selected it. Only code for this particular form was setting the ColumnHidden property to true for two fields. Commented that out and wouldn't u know. Magic. Goodness gracious. That was definitely gonna drive me crazy. Thx Guys...