![]() | ![]() Products ![]() ![]() ![]() ![]() |
Home » Technical Support » ElevateDB Technical Support » Support Forums » ElevateDB Enhancement Requests and Suggestions » View Thread |
Messages 1 to 2 of 2 total |
![]() |
Mon, Nov 19 2012 1:14 PM | Permanent Link |
Barry | It would be nice if we could reference any row value(s) in the Custom Constraint error message.
So if a constraint was violated, we could have a message defined like: 'The State_Code "[State_Code]" is invalid because it does not exist in the States table". The "[State_Code]" gets replaced with a column value from the table whose row was rejected. The error message could have several column references from the row. This will give the user a better description (more dynamic) of what went wrong than a canned answer. The less thinking the user has to do when an error occurs, the fewer calls to tech support. ![]() Of course these column reference(s) would have to be maintained by EDB if we rename "State_Code" column to something else like "StateCode" etc.. This minor enhancement could make for a more friendly end-user application by putting more "smarts" into the application at the database level. Barry |
Wed, Jan 2 2013 5:42 AM | Permanent Link |
Tim Young [Elevate Software] Elevate Software, Inc. ![]() | Barry,
<< This will give the user a better description (more dynamic) of what went wrong than a canned answer. The less thinking the user has to do when an error occurs, the fewer calls to tech support. ![]() I'll see what I can do, thanks. Tim Young Elevate Software www.elevatesoft.com |
This web page was last updated on Wednesday, July 2, 2025 at 06:46 PM | Privacy Policy![]() © 2025 Elevate Software, Inc. All Rights Reserved Questions or comments ? ![]() |