Alternatives to databinding

  • Thread starter Thread starter Matt Burland
  • Start date Start date
M

Matt Burland

I think I'm going to abandon using databinding in my windows forms project
because it simply doesn't work as well as it ought to. There are simply too
many road blocks and too much odd are poorly documented behavior to be worth
my time any more. I patched up and worked around so many of the oddities in
framework that I don't even feel like I still in control of the code
anymore. So I'm ditching it (*I think*).
Now I need to work out an alternative scheme for getting data from my
datasource into the controls on my form and back again, so my question is
does anybody know of any good articles or tutorials on this subject. I want
to try and make sure I've considered everything before I start what might be
a major undertaking so I can decide on the most elegant and flexible
solution.

Cheers

Matt
 
Matt Burland said:
I think I'm going to abandon using databinding in my windows forms project
because it simply doesn't work as well as it ought to. There are simply too
many road blocks and too much odd are poorly documented behavior to be worth
my time any more.
Click to expand...
just jumped on the thread to say: "I'm right behind you!" and "GOOD LUCK!"
I patched up and worked around so many of the oddities in
framework that I don't even feel like I still in control of the code
anymore.
Click to expand...
ha! too true...
So I'm ditching it (*I think*).
Click to expand...
wish i could join you here - but i have no time to rewrite my own at this
point, so i'm trudging ahead with the hax...
Now I need to work out an alternative scheme for getting data from my
datasource into the controls on my form and back again, so my question is
does anybody know of any good articles or tutorials on this subject. I want
to try and make sure I've considered everything before I start what might be
a major undertaking so I can decide on the most elegant and flexible
solution.
Click to expand...
sorry, i have nothing to offer other than advice:

some background sure couldn't hurt, but if you have already identified the
inadequacies you are trying to overcome, then you probably have more of a
design foundation at this point than you might think.

one way to look at it: when all is said and done, a poorly-planned,
poorly-implemented, poorly-documented, idiosyncrasy & inconsistency-ridden
approach written by *YOU* is still probably going to be 100 times easier to
work with than the poorly-planned, poorly-implemented, poorly-documented,
idiosyncrasy & inconsistency-ridden approach written by M$... =P

again, good luck & post back here if you find any leads - lots of people
would probably like to hear about them! =)
 
boo said:
one way to look at it: when all is said and done, a poorly-planned,
poorly-implemented, poorly-documented, idiosyncrasy & inconsistency-ridden
approach written by *YOU* is still probably going to be 100 times easier to
work with than the poorly-planned, poorly-implemented, poorly-documented,
idiosyncrasy & inconsistency-ridden approach written by M$... =P
Click to expand...

Good point, at least I understand my own madness (sort of).....mwah ha ha ha
ha ha
 
Hi Matt,

I'd start by filling a datasource of the data you need in the form. Then
create a dataview of the datatable and sort it in a manner consistent with
what ever search needs may exist. Say entering text in a textbox and
clicking a button requests displaying the qty in a disabled textbox for the
account number entered in the textbox. Sort the dataview on account #; in
the click event search for the row in question and simply assign the value
to the disabled textbox's text property.

HTH,

Bernie Yaeger
 
Back
Top