Validation Rule

[AndyK]

Hi All,

I want to set up a validation rule to restrict entries on a text field to
the folloiwng format:

Friday, 4 April 2005

Thursday, 11 January 2005

Any ideas. I have tried a rule along the lines of

Like "*day," but this does not do the job.

Cheers,

Andy

 

[Joseph Meehan]

Hi All,

I want to set up a validation rule to restrict entries on a text
field to the folloiwng format:

Friday, 4 April 2005

Thursday, 11 January 2005

Any ideas. I have tried a rule along the lines of

Like "*day," but this does not do the job.

Cheers,

Andy

Why not use a date field and then display the data anyway you want?

 

[AndyK]

The date field does not work with my input form. I have had trouble with a
date picker. It works with a text field but not a date field. Thanks anyway.

 

[Allen Browne]

Access will spin the entry around if it does not make sense in the format
expected. For example, if you enter:
29/2
this year, Access spins it around to 1 Feb 2029, because that's as much
sense as it can make of the entry.

You cannot force the user to enter the date in that format unless you use an
unbound control, or a combo where the bound column is zero-width.

Not that it makes sense to try: it would take far too many keystrokes to
force the user to enter the long date.

If you are trying to prevent problems with the Australian date format, see
this article:
International Date Formats in Access
at:
http://allenbrowne.com/ser-36.html
It comes from 12 years experience working with Access in Australia.

 

[Joseph Meehan]

Access will spin the entry around if it does not make sense in the
format expected. For example, if you enter:
29/2

That would be true but Andy is using a text field type not date.

 

[Joseph Meehan]

The date field does not work with my input form.

That is interesting. What seems to be its problem?

 

[Allen Browne]

Yes, you're right. He did say this was a texrt field.

I wonder why he is doing that, and then trying to force only dates into the
field. Strange.

 

[Joseph Meehan]

Yes, you're right. He did say this was a texrt field.

I wonder why he is doing that, and then trying to force only dates
into the field. Strange.

That's what I am wondering about. It sounds like doing it the hard way
and will regret it later.

 

[AndyK]

It won't write to the date field. I simply get a message tellig me that the
query is not updateable. I guess it is a probnlem with the code and my
limited experience has not allowed me to fix it/

Andy

 

[AndyK]

Thanks. A great article.

Access will spin the entry around if it does not make sense in the format
expected. For example, if you enter:
29/2
this year, Access spins it around to 1 Feb 2029, because that's as much
sense as it can make of the entry.

You cannot force the user to enter the date in that format unless you use
an unbound control, or a combo where the bound column is zero-width.

Not that it makes sense to try: it would take far too many keystrokes to
force the user to enter the long date.

If you are trying to prevent problems with the Australian date format, see
this article:
International Date Formats in Access
at:
http://allenbrowne.com/ser-36.html
It comes from 12 years experience working with Access in Australia.

 

[AndyK]

I reckon your right. It was a last ditch effort. I am using a date picker to
enter via an asp web page to an access database. I set the database up with
a date field but could not write to it using the date picker. I am sure my
coding was wrong here, but as a result I resorted to uisng a text field. It
writes to the tect field without any problems.

Sorry if I appear to be a bit of a moron. If you can help that would be
great.

Andy

 

[Joseph Meehan]

It won't write to the date field. I simply get a message tellig me that
the query is not updateable. I guess it is a probnlem with the code and my
limited experience has not allowed me to fix it/

It sounds like a relationship problem. Take a look at the relationships
involved all the way back to the tables where the data is stored. I suspect
you will find that due to the relationships Access does not know what to do
with any changes due to the relationships and updateable questions.

 

[AndyK]

Thanks. Will look at that. The input form is an ASP page. Not sure of the
problem is there.