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]

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

 

[John]

I have next and prev queries added to data adapter that only pick one record
at a time using TOP 1. I save every time user moves to a different record.
It has the advantage of being scalable and also if other users are adding
records to db they get picked up this way. If picking one record at a time
is too much traffic, try more records at a time such as TOP 100 or TOP 200
whatever suites you.

Regards

 

[JimmyKoolPantz]

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.

My advice is this:

1) Automate as much as you can so you can make your users happy.
Never assume that your program is perfect. Ask the users how they
feel about your program. And ask them if they have any suggestions on
how to make there job easier. Alot of programmers I have worked with
are not very open minded. Their given a task to built it but they
don't care how the users feel. Build the program around the users
needs. I personally like to use my programs, and do exactly what the
users are doing with it. Once you use it a few times you will get a
feel on what you need to improve.

2) If they are typing in a lot of information I would defenately test
for data validation. Make sure they are entering the correct
information before it gets shipped over to the database. If a field
is supposed to be numeric, check to see if it is numeric. If a field
it required make sure that its been populated. So when they hit that
button, go directly to a "validation routine".

3) As far as the database goes, you need to ask yourself a few
questions like. Wheres the database going to be stored? How big is
this database going to get? How many people are going to be using it,
or needing it? How secure does the database need to be? I've stored
Data In various different file types. I've used .txt, .csv, .mdb
(access), .dbf and also sql databases. It seemed like almost all of
them were hard to manage, except for SQL. Sometimes databases get
alot larger than i expect, a user would somehow move a folder or
delete my database completely, everything that can go wrong will
sometmes go wrong.

Finally, I would have to say create the database using SQL, and access
the database using StoredProcedures, I think its the best way to go.