Glad to hear you reckon it can be fixed. Will save me a trul massive amount of reworking.
To clarify then (and let's use an example of 1st May 2009 - or 01/05/2009 as I would want it):
My form does have a note that users should enter dd/mm/yyyy. i.e. 01/05.2009.
i quite appreciate that if someone mistakely enters 05/01/2009 that that's a valid date and no amount of validation would throw it up as incorrect, as opposed to someone entering 21/20/009, which i can validate out ok. if they put in 05/01/2009 that's a user error and that's that....
but currently, users are entering 01/05/2009 and getting 05/01/2009 written to the dBase - and then not on all pages for some reason. this date issue is made more acute since the records inserted are college events and Univ Mail is set up to auto-email them to relevant parties. so not only will administrators not know date's been reversed until they go to the detail page after inserting, an email is also going out with an incorrect date on it. (or at least it would if it wered all live - and it has to go live next week one way or the other)
all i want is that when someone enters 01/05/2009, that's what get's written to the dBase - that DataAssist inserts ands renders faithfully the date as it has been input
and that that's what shows on other pages. and that it's consistent across all instance thereof. if someone puts in mm/dd/yyyy despite being told otherwise, that's their problem!
(tho that's highly unlikely).
hope that clarifies things - and thanks for your continued assistance in getting this to some satisfactory conclusion Ray.