best pratice for DB User interface

[OSI Mik]

Hello,
I try to make a user interface for a DB in VB.DOT 2005 with SQL server.
I use auto generate Textbox and datagridview (with BindingSource,
TableAdapter... ) with manual add of ComboBox and I have a lot of trouble
when I must change my DB structure and sometime VB lost the link between my
dataset and my component. (certainly a bad choice in my object naming....)
I would like to know :
What is the best way to make user interface with DB ?
How make a easy validation (max size / not empty / valid foreign key) on
input data when there a lot of textbox ?

If existing objects can do that (free or not) it's better, else I will try
to generate it.
Thank you for your help.
Osi Mik

[DArnold]

Re: best pratice for DB User interface

OSI Mik wrote:

Hello,
I try to make a user interface for a DB in VB.DOT 2005 with SQL server.
I use auto generate Textbox and datagridview (with BindingSource,
TableAdapter... ) with manual add of ComboBox and I have a lot of trouble
when I must change my DB structure and sometime VB lost the link between my
dataset and my component. (certainly a bad choice in my object naming....)
I would like to know :
What is the best way to make user interface with DB ?

It's not to allow the user interface to directly to interact with the
database.

How make a easy validation (max size / not empty / valid foreign key) on
input data when there a lot of textbox ?

You have the code in a business object that does the validation when
user tries to save the object, preferably a business object that has the
data persist logic in it as well, using SQL Command Objects, instead of
dataadapters, datasets and recordsets, etc, etc. You bind a business
object or a collection fo business objects to a control.

>
If existing objects can do that (free or not) it's better, else I will try
to generate it.

Solutions like NHibernate that works with something like CSLA Business
Objects.

On there other hand, you can use the CSLA Framework to understand and
make the base core of objects yourself that are needed to produce a
viable solution that has Opps design concepts.

http://www.lhotka.net/Article.aspx?id=1351540e-b941-446a-bacb-e0059cc82ee7

[OSI Mik]

Re: best pratice for DB User interface

Thank you for your anwser, I will try to apply it.
Osi Mik

"DArnold" <DArnold@DArnol d.coma écrit dans le message de news:
eZXcYAAtHHA.419 6@TK2MSFTNGP03. phx.gbl...

OSI Mik wrote:

>Hello,
>I try to make a user interface for a DB in VB.DOT 2005 with SQL server.
>I use auto generate Textbox and datagridview (with BindingSource,
>TableAdapter.. .) with manual add of ComboBox and I have a lot of trouble
>when I must change my DB structure and sometime VB lost the link between
>my dataset and my component. (certainly a bad choice in my object
>naming....)
>I would like to know :
> What is the best way to make user interface with DB ?

>
It's not to allow the user interface to directly to interact with the
database.
>

> How make a easy validation (max size / not empty / valid foreign key) on
>input data when there a lot of textbox ?

>
You have the code in a business object that does the validation when user
tries to save the object, preferably a business object that has the data
persist logic in it as well, using SQL Command Objects, instead of
dataadapters, datasets and recordsets, etc, etc. You bind a business
object or a collection fo business objects to a control.
>

>>
>If existing objects can do that (free or not) it's better, else I will
>try to generate it.

>
Solutions like NHibernate that works with something like CSLA Business
Objects.
>
On there other hand, you can use the CSLA Framework to understand and make
the base core of objects yourself that are needed to produce a viable
solution that has Opps design concepts.
>
http://www.lhotka.net/Article.aspx?i...b-e0059cc82ee7