How does data-binding controls affect scalability?

[tfong]

Hi,

I'm currently working on an distributed n-tier project, and I've been looking for an unbound hierarchical data grid control, but there don't seem to be too many of them around.

So that raised the question, how does data-binding affect the scalability of an application?

I've always assumed that apart from being hard to debug, data-bound stuff was not so scalable.

What are everyone's views?

Thanks,

tfong

[HunterMcCray]

Originally posted by tfong
Hi,

I'm currently working on an distributed n-tier project, and I've been looking for an unbound hierarchical data grid control, but there don't seem to be too many of them around.

So that raised the question, how does data-binding affect the scalability of an application?

I've always assumed that apart from being hard to debug, data-bound stuff was not so scalable.

What are everyone's views?

Thanks,

tfong

The general wisdom seems to be that data bound objects are the mark of non-proffesional apps, and that they allow too many chance occurances while embedding lots of overhead. I think that the programmer has to decide how to proceed after weighing the time and effort to code an object VS the importance of making it work NOW. If you are writing an app for less than X number of users, and you are going to admin the database and speed and size of your program are not required to be max/min (ed) then there are times when it makes a great deal of sense to "cheat". On the other hand if you are writing a front-end for a large number of users then it makes sense to eliminate any chance of screw-ups. I often start with a data bound control and object and then migrate toward a code based counter part. Many times the data bound object works just fine, and I let it go. I only write code for in-house apps where I have hands on experience with the day to day use of the program, and if it isn't broke then I don't mess with it. I think that it is important to realize that not all apps need to be bullet proof examples for VB Journal. Sometimes it is better to buy a cheap cart than to build a custom one from scratch.

Just an opinion, probably not popular with the Proffesionals,

Hunter

if you use a disconnected recordset and limit the
number of records to a reasonable amount, there is
not much to speak against bound grids. you will need
a solid business-logic to handle inconsistencies,
but again this is required anyway.

if i remember right MS Flex Grid (ships with VB) supports
cliping format, so it should be possible to use it
unbound.

good luck

Sascha