DevForce Community Forum : Integer values being 0 http://www.ideablade.com/forum/ This is an XML content feed of; DevForce Community Forum : DevForce Classic : Integer values being 0 Thu, 11 Jun 2026 04:47:59 -700 Fri, 25 Apr 2008 10:01:34 -700 http://blogs.law.harvard.edu/tech/rss Web Wiz Forums 9.69 360 www.ideablade.com/forum/RSS_post_feed.asp?TID=780 DevForce Community Forum http://www.ideablade.com/forum/forum_images/IdeaBlade_logo_tm.png http://www.ideablade.com/forum/ Integer values being 0 : Number 1 is an interesting idea... http://www.ideablade.com/forum/forum_posts.asp?TID=780&PID=2877#2877 Author: DataMan
Subject: 780
Posted: 25-Apr-2008 at 10:01am

Number 1 is an interesting idea because then if what you set in code for the value to be isn't what the user wants they will change it.
 
Number 2 - I've looked into this and while it works really well I was assuming that when i called the instance verification that it would turn on the ErrorProvider on the form for the field that failed.  Without me doing some research and taking the easy way out by asking you :-) Is there any way to, upon verification, get the errorproviders flashing for items that don't validate?
 
Thanks
 
]]> Fri, 25 Apr 2008 10:01:34 -700 http://www.ideablade.com/forum/forum_posts.asp?TID=780&PID=2877#2877 Integer values being 0 : Creating a new entity is one place... http://www.ideablade.com/forum/forum_posts.asp?TID=780&PID=2866#2866 Author: davidklitzke
Subject: 780
Posted: 22-Apr-2008 at 7:49pm

Creating a new entity is one place where some of the properties of a business object can escape verification.  If a property is a required property, it must be initialized in the process of creation.  Furthermore, if it is an integer field, it will be initialized to zero.
 
There are at least two solutions/workarounds to this problem.
 
(1) In the creation code, make sure there are no uninitialized fields that would break verification rules if set to the default value (e.g., an integer field set to 0).  This is the quick (but by no means foolproof) method.
 
(2) Use Instance Verification immediately after creating a business object.  This is the sure way (although it is a little more work).  Read more about Instance Verification in the "Developer's Guide".


Edited by davidklitzke - 22-Apr-2008 at 7:54pm]]> Tue, 22 Apr 2008 19:49:57 -700 http://www.ideablade.com/forum/forum_posts.asp?TID=780&PID=2866#2866 Integer values being 0 : I have a form with a textbox on... http://www.ideablade.com/forum/forum_posts.asp?TID=780&PID=2859#2859 Author: DataMan
Subject: 780
Posted: 22-Apr-2008 at 8:45am

I have a form with a textbox on it (added using devforce) that is tied to an integer field in SQL.

I added a verifier to the field that this textbox is bound to which says that the value is required and the min value is 1.

 
When I add a new record using the create method, the value 0 automatically gets entered into the text box.  If I don’t change that value or tab into the field I am allowed to save the record even though it is 0.  No error message occurs.

 

The same thing is happening with all of my comboboxes that are tied to integer values.

 

Do I need to add my own validation of those text boxes(!=0)/comboboxes(notinlist) and throw an error of my own or is there a way to do it in Ideablade?

 
Thanks
]]> Tue, 22 Apr 2008 08:45:27 -700 http://www.ideablade.com/forum/forum_posts.asp?TID=780&PID=2859#2859