this is not a good practice as it requires an open database connection for an extended period of time, or the opening and closing of a connection for each field change. either way it's a poor utilization of resources.
the concept behind ado.net is to disconnect the user from the database as much as possible. open connection, run sql, close connection.
I have found the unit of work pattern is an excellent concept for managing database connectivity (and transactions).
Jason Meckley
Programmer
Specialty Bakers, Inc.