Looking for tips to help me develop my new project

[Dagoberto Aceves]

Im currently still designing the database I will be working with, and
I've been following all those nifty db pointers that books like to point
out. Anyway, once I finish up with the the tables, Im going to write a
front end with .Net

I've done a coupld of simple trial runs using smalls db and simple sql
statements. Im looking for tips to keep in mind. Since this project is
still in its beginning phase, any problems i can avoid now and not have
to deal with later would be awesome.

Thanks in advance!


*** Sent via Developersdex http://www.developersdex.com ***

[Dennis]

Use Parameters
Use Stored Procedures if possible
Use DataSets to change the data
--
Dennis in Houston
"Dagoberto Aceves" wrote:

Im currently still designing the database I will be working with, and
I've been following all those nifty db pointers that books like to point
out. Anyway, once I finish up with the the tables, Im going to write a
front end with .Net

I've done a coupld of simple trial runs using smalls db and simple sql
statements. Im looking for tips to keep in mind. Since this project is
still in its beginning phase, any problems i can avoid now and not have
to deal with later would be awesome.

Thanks in advance!


*** Sent via Developersdex http://www.developersdex.com ***

[Cor Ligthert [MVP]]

Dagobert,

Start with developing your procedures for concurrency errors. If you have to
implement that at the end it is probably to late.

Just my idea

Cor

[Dennis]

Cor, I found your reply interesting and probably very true. Do you have an
example code excerpt of handling a concurrency error?
--
Dennis in Houston
"Cor Ligthert [MVP]" wrote:

Dagobert,

Start with developing your procedures for concurrency errors. If you have to
implement that at the end it is probably to late.

Just my idea

Cor

[Cor Ligthert [MVP]]

Dennis,

I don't have it, and if I had it, I would not give it. This is for me a part
of security where I never give answers about than tell that it has to be
done.

For the rest it can be for everybody another problem.

You have to communicate with your user what shall be done.

Reject all changes; can be easily with connection.rollback
Reject the changes; partially therefore you use the get changes and the
merge
Give a suggestion to the user to change a part of that get changes and try
it again
etc. etc.

However the method as to be consistent.

Just my thought,

Cor

[Dennis]

Thanks. I wasn't sure what you meant "check for Concurrency Errors"
--
Dennis in Houston
"Cor Ligthert [MVP]" wrote:

Dennis,

I don't have it, and if I had it, I would not give it. This is for me a part
of security where I never give answers about than tell that it has to be
done.

For the rest it can be for everybody another problem.

You have to communicate with your user what shall be done.

Reject all changes; can be easily with connection.rollback
Reject the changes; partially therefore you use the get changes and the
merge
Give a suggestion to the user to change a part of that get changes and try
it again
etc. etc.

However the method as to be consistent.

Just my thought,

Cor