Show date pick always

[Dick7Access]

Is there a way to have the date picker show always, without having to click on the date control?

 

[ashleedawg]

You can have the date picker pop up automatically when the control is selected:

In the control's On Got Focus event place this code:

DoCmd.RunCommand acCmdShowDatePicker

...but I don't think you can have it always displayed. (Not the built-in control anyhow.)

 

[Dick7Access]

You can have the date picker pop up automatically when the control is selected:
...but I don't think you can have it always displayed. (Not the built-in control anyhow.)

Yeh! that's the best I can do right now. When they hit new record button I have it go to the date control and the date picker shows up, but I was trying to make it idiot proof. I also put a label under the control that says, " click in the white to bring up calendar."

 

[Galaxiom]

I was trying to make it idiot proof.

Impossible, idiots are far too ingenious.

 

[isladogs]

You will need to replace it with your own custom control.
I did so for much the same reason as you
You then need to ensure the built in date picker is set to never display

My version is available here
https://www.access-programmers.co.uk/forums/showpost.php?p=1533910&postcount=2

Ignore the code in that post. Just use the attachment

 

[missinglinq]

When they hit new record button I have it go to the date control and the date picker shows up, but I was trying to make it idiot proof. I also put a label under the control that says, "click in the white to bring up calendar."

That doesn't sound as if you have the DatePicker actually opening, when the Control is entered, which is what ashleedawg's code would do. As he suggested, using

Private Sub YourDateField_GotFocus()
  DoCmd.RunCommand acCmdShowDatePicker
End Sub

will automatically popup the DatePicker, when the Control is entered, without the user doing anything. Don't know how much more idiot-proofing you could do. OF course, the problem with idiot-proofing anything is that idiots are so darn ingenious!

Linq ;0)>

 

[Dick7Access]

That doesn't sound as if you have the DatePicker actually opening, when the Control is entered, which is what ashleedawg's code would do. As he suggested, using

Private Sub YourDateField_GotFocus()
  DoCmd.RunCommand acCmdShowDatePicker
End Sub

will automatically popup the DatePicker, when the Control is entered, without the user doing anything. Don't know how much more idiot-proofing you could do. OF course, the problem with idiot-proofing anything is that idiots are so darn ingenious!

Linq ;0)>

Can't rspond. #WLOS (wife looking over shoulder)

 

[ashleedawg]

of course, the problem with idiot-proofing anything is that idiots are so darn ingenious! Linq ;0)>

Image attached:

 

[Dick7Access]

I have indexed (no duplicates) on the date field. When I datepick a date that already has data, the date picker will accept the date, but wipes out the data in the previous record with that date. How do I make it not accept a used date? I need only one record per date.

 

[missinglinq]

Image attached: View attachment 66693

Love the graphic!

Linq ;0)>

 

[missinglinq]

...How do I make it not accept a used date? I need only one record per date...

Usually done by checking the Records in the Table for the given Date...like this:

Private Sub YourDateField_BeforeUpdate(Cancel As Integer)

If DCount("*", "YourTableName", "YourDateField = #" & Me.YourDateField & "#") > 0 Then
  Cancel = True
  MsgBox "There is Already a Record for this Date! Please Pick Another Date"
  Me.YourDateField.Undo
 End If

End Sub

Linq ;0)>

 

[ashleedawg]

Perhaps you could solve both issues by using a listbox, populated ("on load") with only "available" dates. It's always visible, and forces the user to pick a date that's going to work.

(And you could make it blink with big red arrows pointing at it... Maybe that's pushing it though....)

 

[Dick7Access]

Why doesn't this code work?

Private Sub diaryDate_AfterUpdate()
DoCmd.GoToControl "diaryData"
End Sub

What else do I need to do?

 

[Dick7Access]

trying some more idiot proofing,

Private Sub cmdFindMonth_Click()
DoCmd.ApplyFilter "qryFindMonth"
DoCmd.OpenForm "frmEveningClutter", acFormDS   ' Opens form in datasheet view
Me.cmdAll.Enabled = False
Me.cmdNew2.Enabled = False
End Sub

I am disabling two other command buttons so they can't crash if they try to click cmdNew2 or cmdAll all after they have already clicked cmdFindMonth.

Is there anyway to have a msgbox tell them that they have to pick a month if they try to click cmdNew2 or cmdAll after they already clicked cmdfindMonth?

 

[Cronk]

I believe data validation is critical to avoid missing data and maintain data integrity.

In your button events, you could call a DataValidation function which returns true if all rules are satisfied.

if len(me.txtDateControl & "") <1 then
   msgbox "Date is missing"
   me.txtDateControl.setfocus
   exit function
endif

Include other tests as necessary ie start date is before end date.

I occasionally get called back to a system working for years where it begins crashing and I find it's some such validation test that I did not deem necessary.

I call these PEBCAK errors (problem exists between chair and keyboard). Something a bit like ID ten tee errors (ID10T). But hey, where would we be without our users?