Error Message re: data entry of date

[Pro-not]

Hi! First post here and I hope someone can help me. Sorry if this has been put under the wrong topic.

I have a temp entering data into the database. She cannot enter data from May 2010 because she is getting a window popup that states "date verification (error) - "date entered in older than 30 days". All data is able to be entered except this one column/field that contains the date. The data is being entered in designview and the format is mm/dd/yyyy. I know it must be something under the "properties (?)" that needs to be changed in order to fix the problem.

Can anyone help me?

BTW, glad I found this forum. Kudos!

[pbaldy]

Check in the properties of that field in the table and see if there's a validation rule set up. If not, presuming the user is entering data through a form, check the textbox for a validation rule.

[Pro-not]

Thank you, pbaldy. There is not a validation rule set up in the text box or the properties of that field.

[pbaldy]

Hmm; how about code in the before update event of the textbox?

[Pro-not]

I'll check and be back.

Thanks much!

[pbaldy]

Oh, and the before update event of the form too.

[slave138]

I'm a little confused by this:

...
The data is being entered in designview and the format is mm/dd/yyyy
...

[Pro-not]

pbaldy, you fixed the problem. Thank you very much.

Under properties, under the date field, there was nothing in the "before update", however there was something listed in the "after update". When I took that information out and left it blank, it allowed me to enter ANY date (be it 60 or 90 or 100 days old) without getting an error warning.

You are a jewel. Thanks much!

A pro I am not!

[Pro-not]

I'm a little confused by this:

Most folks do enter data via a created form. I am having the data entered via datasheet view instead of form view. You are correct, my goof. Not design view. Whew....

[pbaldy]

Glad we found the issue. Generally the before update event is used for data validation, but you can kludge it with the after update event, which apparently was done here.