Re: Back-End Vs Front-End

Comments in-line.

AcCeSsDeNiEd wrote:
> Hi,
>
> What is the norm when a front-end programmer (e.g VB) designs an interface for a database (e.g
> Oracle)?
>
> Specifically, I mean should the front-end programmer hard-code constraints like null/nullable fields
> into his/her interface, or should he/she just output the meaningless Oracle errors to the user? (e.g
> via the VB interface).

Best practices, in terms of what you are asking, are rarely product specific.

> I was thinking there are good and bad things about the front-end programmer hard-coding/duplicating
> the "controls" into their program.

Rarely.

> The bad: if the DBA un-nulls a field on the Oracle DB, the front-end will still insist on a input of
> data for that field. The DBA must tell the programmer to do some re-coding and re-compile the
> front-end.

The data belongs to the database ... not the interface.

> The Good: if certain fields need to be unnulled (e.g for some data-migration), it will not affect
> the front-end. That means data-entry staff can continue to data-entry and all the "checks" will
> still in be place.
>
> So what is the norm?

The norm is for the expert on data and databases to make these decisions.

Should the front-end designer wish to enforced some constraints locally, in addition to the back-end constraints, that is a duplication: not a replacement.

-- 
Daniel A. Morgan
http://www.psoug.org
damorgan_at_x.washington.edu
(replace x with u to respond)