Reducing Code Maintainence for ADO projects ?

Does anyone use an efficient codeing method to reduce the amount of rework
that goes one when you want to change the number of fields in a table.

You know, you spend lots of time sorting out your coding for command
objects especially the update and insert ones. Then you find you need to add
or delete a field command builder helps is fallable.

Is there an easier or at least better way ? Im interested to learn new
approches to this issue

--
Regards - One Handed Man

Author : Fish .NET & Keep .NET

==============================