Access 2013 Datepicker problem

[jpg250]

I have a recent problem where my application keeps running out of memory (runtime error '3035' System resource exceeded.) I have narrowed it down to where a datepicker is opened. In the windows task manager before the datepicker is used, memory used by MSACCESS.EXE shows as 26,000k. As soon as i open the datepicker, and leave it in an opened state for any length of time, it starts chewing up memory (very fast as well) until it reaches about 1.4 Gb, when it stops increasing. If I try do do anything else after that, I get the error message.



I checked in debug that no code is actually running while this is happening.

I would appreciate help from anybody who has experienced similar problems with the datepicker, and has a solution.

[Missinglinq]

Are you talking about the native DatePicker that pops up when you enter a Control tied to a DateTime Field? If so, first question that comes to mind is why would leave it in an opened state for any length of time...rather than simply picking a date and moving on?

That aside, the Textbox Control could be corrupted, I suppose. Although we usually think of Forms, and even entire Databases, when we speak of corruption, Controls, such as Textboxes and Comboboxes, can and do become corrupted, and seem particularly susceptible to this during app development. The test/cure for this is short and simple...delete and then re-create the Control.

Linq ;0)>

[jpg250]

Thank you Missinglinq. You solved my problem. I ended up deleting and re-creating the whole form instead of just the Textbox, but the problem has gone away now,

[Sundtec]

We are having the same problem with Access 2013 32bit. Create a new blank form, add a text box control with date format. Set show date picker = For dates.
Load task manager, select processes tab and watch the memory column for msaccess.exe.
View the form in form view, click on the calendar fly out. Memory starts increasing for msaccess and does not stop until resources are depleted.
Anyone know what’s going on?