Tek-Tips is the largest IT community on the Internet today!
Members share and learn making Tek-Tips Forums the best source of peer-reviewed technical information on the Internet!
-
Congratulations Chriss Miller on being selected by the Tek-Tips community for having the most helpful posts in the forums last week. Way to Go!
How Can i Change the message "INVALID INPUT" 3
- Thread starter ivancs
- Start date
-
2
- #2
Ivancs,
Your question is too vague to answer. I have looked, and I don't see any FoxPro error message that reports "Invalid Input". This leads me to belive one of two things either: a) This is not a FoxPro message, in which case, I'm not sure there is a lot you can do about it, or b) This is an error message generated by code that someone has written. I assume in this case as well, that you are not the author of the application.
In the latter case, there are a number of places to look. "Invalid Input" leads me to believe that this is a field validation, and for whatever reason the data placed in the field is not valid data. Check your VALID clause on the field in this case, to see if there is code that does immedate checking of data enterd. This may also lead you to an error checking routine, which could be in a number of places. If it is capturing a real FoxPro error, you need to look in the ON ERROR routine, to see what "Invalid Input" translates to. (It has to be captured via the some function like ERROR(), or MESSAGE(). That may be caputred, and then replaced with custom error reporting. Usually this code would be kept in a MAIN, or PROCEDURE file, (as defined by SET PROCEDURE TO <procname>. The last place is, the code for this could be in the physical Screen Set (assuming this is a screen set), in the CLEANUP & PROCEDURES section. (Go to Screen, Layout, Code, Cleanup & Procedures).
If you can provide more information about OS, and the application, and what happens when you recieve this error message, I may be able to be more helpful.
Cheers,
-Scott Payton
Your question is too vague to answer. I have looked, and I don't see any FoxPro error message that reports "Invalid Input". This leads me to belive one of two things either: a) This is not a FoxPro message, in which case, I'm not sure there is a lot you can do about it, or b) This is an error message generated by code that someone has written. I assume in this case as well, that you are not the author of the application.
In the latter case, there are a number of places to look. "Invalid Input" leads me to believe that this is a field validation, and for whatever reason the data placed in the field is not valid data. Check your VALID clause on the field in this case, to see if there is code that does immedate checking of data enterd. This may also lead you to an error checking routine, which could be in a number of places. If it is capturing a real FoxPro error, you need to look in the ON ERROR routine, to see what "Invalid Input" translates to. (It has to be captured via the some function like ERROR(), or MESSAGE(). That may be caputred, and then replaced with custom error reporting. Usually this code would be kept in a MAIN, or PROCEDURE file, (as defined by SET PROCEDURE TO <procname>. The last place is, the code for this could be in the physical Screen Set (assuming this is a screen set), in the CLEANUP & PROCEDURES section. (Go to Screen, Layout, Code, Cleanup & Procedures).
If you can provide more information about OS, and the application, and what happens when you recieve this error message, I may be able to be more helpful.
Cheers,
-Scott Payton
-
1
- #3
"Invalid Input" is reported when you return .F. from a VALID() clause. To fix this, return O (zero), after you have used a wait window or MSGBOX() [in FOXTOOLS.FLL] to display the message you want in whatever language you choose.
The only other place I recall this message comes up, is in a text Get, that's defined (initialized) with a Date variable, and the user keys in an non-valid date. In this case you'll have to use a character field and do your own editing/validation to trap these messages.
Rick
The only other place I recall this message comes up, is in a text Get, that's defined (initialized) with a Date variable, and the user keys in an non-valid date. In this case you'll have to use a character field and do your own editing/validation to trap these messages.
Rick
See this these give you any ideas. look for the line
on readerror JUNK = MSGWWAIT(....)
*
David W. Grewe
Dave@internationalbid.com
ICQ VFP ActiveList #46145644
on readerror JUNK = MSGWWAIT(....)
*
David W. Grewe
Dave@internationalbid.com
ICQ VFP ActiveList #46145644
ivancs, this error is displayed in a window message when a valid procedure return .f. in a get routine. You can change this using the <error> option in the editing window of the field, or if you are writing code manually, you should write something like this:
get [varmem] valid [funcion_of validation] error "message"
where "message" is the text to display instead of "invalid input"
good luck...
get [varmem] valid [funcion_of validation] error "message"
where "message" is the text to display instead of "invalid input"
good luck...
- Status
Similar threads
- Locked
- Question
