Best way to develop a database program

[HDI]

Hi,

I'm looking for the most user friendly way to develop a database
program.
Maybe some of you have got some nice experience and ideas that I can
use.

I always worked with sql statements te get and put data in the
database. For small applications it will work well to make add, change
and a delete buttons but when a user has got a lot of data on his
screen it feels wrong. The user has to put in all the data and when
he's done he has to press on the save (change) button. I don't think
that last step is user friendy. If something happens or there is a
data concurreny or ... he has to insert all the data again.

So I was thinking of working like MS Access does. When data changes
write it to the database. The disadvantage is that there will be more
traffic.

How do you work?

I'm working with vb2005 express and sql server.

[Michael C]

Re: Best way to develop a database program

"HDI" <hdinf@hotmail. comwrote in message
news:e55506ba-684a-489e-b893-67c76d27fe64@l3 9g2000yqn.googl egroups.com...

Hi,
>
I'm looking for the most user friendly way to develop a database
program.
Maybe some of you have got some nice experience and ideas that I can
use.
>
I always worked with sql statements te get and put data in the
database. For small applications it will work well to make add, change
and a delete buttons but when a user has got a lot of data on his
screen it feels wrong. The user has to put in all the data and when
he's done he has to press on the save (change) button. I don't think
that last step is user friendy. If something happens or there is a
data concurreny or ... he has to insert all the data again.
>
So I was thinking of working like MS Access does. When data changes
write it to the database.
>
How do you work?

Either way is appropriate depending on the situation. In some cases writing
the data as you go is not good for the user as they don't get to play around
and then not save their changes. But in some cases they don't need to play
around.

The disadvantage is that there will be more
traffic.

And this can lead to a slower app for the user. With a large number of users
you might find moving between rows to be slow (I presume you'll save when
they leave the row)

Basically there is no right or wrong answer.

Michael