pelikan

just looking at your code, I would imagine that your property needs a Set to persist the new values.

see http://support.microsoft.com/?kbid=823679

why not look for failures? (also consider a good ESL course with emphasis on spelling)

I can think of one really good reason to know IL - in 2.0 you can use the DynamicMethod class to generate functions on the fly and attach them to assemblies - rates 10 on the coolness scale!

(^|&)(?<fieldname>\W+)=(?<fieldvalue>[^&]+)

guess you'll have to get your hands dirty and use interop check out http://support.microsoft.com/default.aspx?scid=kb;en-us;129860

could be amusing in a tragic sort of way

think about the first WHERE clause - top 250 < x starts with first record so you get 1 .. 250. This suggests you should use an ORDER BY in the first select to reverse the sort order.

a) get the char index of the line by sending message EM_LINEINDEX b) set the selection to that point in the control (or the whole line EM_LINELENGTH) with EM_SETSEL or Select(int index, int lenght)

a million lines of code ? man! that's some complex form. and either you've been cranking out a thousand lines of code day for the last three years or you've resorted to 'other methods', best not described in polite company.

you might try filtering or deleteing the offending rows locally.

thought about your problem - couldn't see an easy solution, so I googled it. check out - http://www.codeproject.com/cs/miscctrl/bending_property.asp

whoa! weak is bad.

noticed that too - real slow down on start up. didn't turn on the fire wall (probably noticed ZoneAlarm) - the only real groans of agony seem to come from the malicious hacker corner.

that's why they traffic in Loonies!!