Hi Tony,
the question is : what is your really need ?
If it is easier for you to use a DataBound grid, so use it. I do not see
any reason to not do so.
Several parameters could impact on your decision, there are :
- cost of databound grid (if you do not use the one shipped with VS.net)
- maintenance of thrid-party component. usually after several months or
years, they are dropped down and it is an issue for customers.
- functionalities are enough to cover your needs ? if not, better
develop your own (it will solve cost and maintenance).
HTH,
Al.
TonyJ wrote:
Hello!
There exist different types of grid. We have databound grid which have a
tight connection to the data base table and
we have a grid which is not bound at all to any data base table.
We have used a third party grid called flygrid which is not bound at all.
I just want to know if there are any suggestion or recommendation when NOT
to use a databound grid.
It's much easier to us a databound grid instead of a non databound grid.
//Tony