Hi garret,

>>>Your database back-end should be assigning default values - not your client.
>>
>>Yeah right and I'm the pope.
>>This is the greateses nonsense I've ever heard.

>Ummm... sorry, Your Holiness. Default values should live with the DB whenever possible. What happens if someone comes in with ODBC and appends a record?

So what ? They have to fill in all values. Many default values are application specific, not domain specific and thus are depended on the application settings. Constraints on the database level should watch integrity so that a record could not be saved when a column does meet the constraints.

In some situations there might be different default values for the same column in the same table, since they were inputed from two different views.

How would you handle, appending a record to a view, not knowing what the default value would be when you save it. If in the application the user uses a record is added, the default values should be visible at once, not only after the record has been saved and requeried.

Walter,