> So the only problem I currently have is that is allows me to > insert a form > without any values for my keys or other columns I have > specified as NOT > NULL.
Not NULL is not not empty. You defined the fields in the database as not null with an empty default value. We have no change inside the framework to distiguish between NULL values and empty string values if we get back the data. So inserting empty string is legal. I think the best way to disable storing empty strings in the database is to setup form validation and test for empty fields (field must be required will do this). Then you do not get an database error during insert - you can have nicer message. We should discuss if we should add validation of empty strings for key fields. Regards, Henner ------------------------------------------------------- The SF.Net email is sponsored by EclipseCon 2004 Premiere Conference on Open Tools Development and Integration See the breadth of Eclipse activity. February 3-5 in Anaheim, CA. http://www.eclipsecon.org/osdn _______________________________________________ DbForms Mailing List http://www.wap-force.net/dbforms
