A Microsoft Office (Excel, Word) forum. OfficeFrustration

If this is your first visit, be sure to check out the FAQ by clicking the link above. You may have to register before you can post: click the register link above to proceed. To start viewing messages, select the forum that you want to visit from the selection below.

Go Back   Home » OfficeFrustration forum » Microsoft Access » New Users
Site Map Home Register Authors List Search Today's Posts Mark Forums Read  

"The value entered isn't valid for this field" No longer appears



 
 
Thread Tools Display Modes
  #1  
Old March 29th, 2006, 01:14 PM posted to microsoft.public.access.gettingstarted
external usenet poster
 
Posts: n/a
Default "The value entered isn't valid for this field" No longer appears

All,

I have been implementing some new features in an access database and I
have several date text boxes on multiple forms. It used to pop-up a
messages "The value entered isn't valid for this field" when I
entered an invalid date, now it just freezes me in the form until I
change it to the correct format, without any pop-up messages.

I have been utilizing DoCmd.SetWarnings, but I have checked all code
and it appears that I have turned it back on after I had shut it off.

Further, just for testing sake, I created a DoCmd.SetWarnings True and
set it for the OnLoad event on one of the forms with a date box and
still no pop-up.

Does anyone know how I can get these pop-up messages back?

Thank you
Dave

  #2  
Old March 29th, 2006, 06:10 PM posted to microsoft.public.access.gettingstarted
external usenet poster
 
Posts: n/a
Default "The value entered isn't valid for this field" No longer appears

Dave:

Do you have any code in the form's Error event procedure which might be
intercepting the error and setting the return value of the Response argument
to acDataErrContinue? If for instance you setting the return value of this
argument to this constant to cater for another anticipated data error in the
form without making it conditional on the value of the DataErr argument then
it will catch all data errors and suppress the system message. The DataErr
value for an invalid date would, I think, be 2113, so you could handle this
specifically in the Error event procedure and either return the system
message (acDataErrShow) or you could suppress it and return a custom message
with the message box function.

Ken Sheridan
Stafford, England

"scadav" wrote:

All,

I have been implementing some new features in an access database and I
have several date text boxes on multiple forms. It used to pop-up a
messages "The value entered isn't valid for this field" when I
entered an invalid date, now it just freezes me in the form until I
change it to the correct format, without any pop-up messages.

I have been utilizing DoCmd.SetWarnings, but I have checked all code
and it appears that I have turned it back on after I had shut it off.

Further, just for testing sake, I created a DoCmd.SetWarnings True and
set it for the OnLoad event on one of the forms with a date box and
still no pop-up.

Does anyone know how I can get these pop-up messages back?

Thank you
Dave


  #3  
Old March 29th, 2006, 07:09 PM posted to microsoft.public.access.gettingstarted
external usenet poster
 
Posts: n/a
Default "The value entered isn't valid for this field" No longer appears

Thanks Ken. But it doesn't appear that I have that arguement.
Additionally, I have about 4 forms with text boxesusing a date and they
all do the same thing (Don't pop-up the warning). It seams to be a
database wide problem

  #4  
Old March 30th, 2006, 11:18 AM posted to microsoft.public.access.gettingstarted
external usenet poster
 
Posts: n/a
Default "The value entered isn't valid for this field" No longer appea

Dave:

The only other possibility that springs to mind is that the application is
being opened in a runtime environment, in which you have to incorporate
custom error handling, but from what you say it doesn't sound like that's the
case. Are you sure the dates are truly invalid? Access is a bit too clever
at times and if an invalid date in one international format is vaid in
another it will 'correct' it without any error being raised. If I entered a
date which was invalid here in Europe but valid in the USA for instance, e.g.
07/25/2006 it would convert it to 25 July.

Ken Sheridan
Stafford, England

"scadav" wrote:

Thanks Ken. But it doesn't appear that I have that arguement.
Additionally, I have about 4 forms with text boxesusing a date and they
all do the same thing (Don't pop-up the warning). It seams to be a
database wide problem


 




Thread Tools
Display Modes

Posting Rules
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts

vB code is On
Smilies are On
[IMG] code is Off
HTML code is Off
Forum Jump

Similar Threads
Thread Thread Starter Forum Replies Last Post
What does "The value you entered isn't valid for this field" mean Veeda Using Forms 1 October 12th, 2005 06:24 PM
link a name with ID , so that when ID is entered name appears Neeraj Using Forms 1 September 29th, 2005 03:50 PM
Runtime error 2101 - The setting you entered isnt valid for this property. General Discussion 0 September 29th, 2005 12:58 PM
2003 admin install + sp1 = "not entered a valid product key" none Setup, Installing & Configuration 2 August 25th, 2005 01:35 AM
"You have not entered a valid Product Key" Dave Setting up and Configuration 1 June 3rd, 2004 06:31 PM


All times are GMT +1. The time now is 09:01 PM.


Powered by vBulletin® Version 3.6.4
Copyright ©2000 - 2024, Jelsoft Enterprises Ltd.
Copyright ©2004-2024 OfficeFrustration.
The comments are property of their posters.