Good "pattern" for data entry forms...

[broy]

I am new to .NET Windows Forms but am currently using Visual Studio
2005 primarily with VB.NET. I am in the process of creating an
application that is going to have several different forms that allow
for editing records in a table in my SQL Server 2005 database, each
form serving a different purpose and showing some same and some
different fields. Let's say it's a table called Tickets. My question is
this...

It should be noted that there are business rules associated with
Tickets, and the fields contained therein. Can you suggest a pattern
for these data editing/entry forms which will allow for creating new
records, deleting existing records, and updating existing records? The
pattern would include things like 1) how I should get and store data
for the current record while user is working on it, 2) How should data
be populated into controls on the forms (e.g. databound vs. manually
filled in from some class or dataset, 3) how should I implement
business rules, 4) how I should persist data out to database, etc. Any
guidance would be very much appreciated.

Perhaps there are even online articles on this that you could point me
to, or a good book(s).

 

[AMDRIT]

Check out IssueVision from http://www.windowsforms.net/

In the sample, there are examples of maintaining concurrency and race
contention. It demonstrates use of the Subject/Observer Pattern in
conjunction with the Model View Controller Pattern.

Additionally, Mr. Lhotka put together a framework
http://www.lhotka.net/Articles.aspx?id=bd7a0904-e76d-48c3-a3ab-a8e9d9645c91

There are also generators out there that will help you maintain a consitant
look and feel, define business rules and manage the DML for you.
http://www.dotnetinfowire.com/product.asp?sid=1&stid=&pg= is an example of
such a thing.

All the options have their pros and cons, you will have to determine the
trade-offs.