Change a textbox value in before update throws error

[twgonder]

Continuing on with my form,
I'm trying to alter what a user entered, in a textbox, into a different string/value.
Specifically, if a user enters a date as 13.4.5 16.7.8 then I want it converted to 2013/4/5 16:07:08


(A funny side note, Access doesn't see an error with that input, put it swaps the time for the date and gives an unexpected result)

My function returns a string for the correctly formatted "." date,
but when I try to save it, anywhere, there's a run-time error (debug goes to the highlighted line).
It seems odd that the textbox entry can't be altered.
I've tried the .text, .value, control name and all give the same error.



Am I going about this correctly?
Is this something Access doesn't allow?
Is there a better place to do this than in BeforeUpdate of the control?
I've researched this on Google. and most of the problems/responses don't apply, but the few that do offer no solution.

[June7]

If you want to modify the input, use AfterUpdate event.
Where does sDtInputL come from?

[twgonder]

If you want to modify the input, use AfterUpdate event.
Where does sDtInputL come from?

Most of the threads I read elsewhere, people started with the AfterUpdate, had the same problem and were told to use BeforeUpdate.
There is further validation done after the change (like a range of permitted dates), so the data needs to be written to the various properties before update so it can be canceled.

I'll give it a try anyways.

sDtInputL is a function to modify the entered date.

[June7]

Don't think I've ever needed BeforeUpdate. I use AfterUpdate to modify input. If you want to validate then use BeforeUpdate to either accept or cancel user input. Then use AfterUpdate to make change to user input. Example from my DB:

Private Sub tbxFieldLL_AfterUpdate()
Me.tbxFieldLL = UCase(Me.tbxFieldLL)
End Sub

[moke123]

I think I would be inclined to force the user to input dates in the desired format rather than try to fix an improper entry.

A funny side note, Access doesn't see an error with that input, put it swaps the time for the date and gives an unexpected result)

Are you still using Date/Time extended?

[twgonder]

@ to all Thanks for the suggestions. I got a prototype that I'm testing now that seems to do most everything I wanted with entry validation, save validation and date entry. I would have liked to be able to enter early CE and BCE dates for historical figures and events, but that will have to wait for another day.