> > > > > > Hello Tore,> > > > Some experts also said before openly here to avoid using DE. However, I have been using DE for a long time now and I haven't experienced any problem with it. And AFAIK no one explained "why" we should avoid using DE, only that most says avoid it. Care to share some of the problems it may cause?> > > > > > http://sandstorm36.blogspot.com> > http://weblogs.foxite.com/sandstorm36> > Aside from what Tore and Stefan has already mentioned. Take a look at the concept of loosely-coupled systems or client/server separation concepts. The DE has made data and UI so very tighly-coupled which diminishes control although sometimes easier to use. The controls (i.e. textboxes that are created by dragging them from the DE has made the UI very dependent to the data. It may seem easier to do, but, in a large-scale and loosely-coupled environment, such an approach is not ideal. > > The higher the level you separate concerns from your data and UI, the better performing your applicaton will be.

I agree with you on this Tom. I also do not like the bound controls created by drag and drop approach from DE. So I never utilize it that way.