perhaps you don't even need sql server. Some earlier version of MS Access
DB design and programming has nothing to do with front-end programming.
I usually work hard on DB design and coding. Enforcing relationships, etc..
Then I can simply raise error to the client and do sloppy work on
But seriously, when integrating different systems, creating different
front-ends, etc.. properly designed DB is
the best testing tool for front-end developers :-)
"sender" <userdomain.com> wrote in message
news:0eed01c34593$162e2da0$a001280aphx.gbl...> When we develop a package using front end like Visual
> Basic etc. then we can write code to validate what kind of
> data the user can enter, save, update or delete. For
> example, if we want the Name should not be greater than 20
> characters, we can write code for this validation. If we
> want that EmpID should be unique, we can write code for
> this. If we want that Salary should always be a positive
> number. I mean we can write code to completely manage how
> the data should be delete/saved/updated in our database.
> Now my questions is then why do we have to the double
> work. Then where is the need to define the constraints
> (column level or table level) in the database tables if
> everything we can do in the Front-end development
> language. Also, even we if we define the constraints in
> the database tables still to check whether there is any
> violation of those constraints we have do write code in
> front-end application at least to trap the error to know
> constraint failed?