>Again I thank you for your responses.
>
>All the solutions I thought were fixing the problem have eventually failed. I must have some bad MoJo in this form .
>
>I have solved the bleed through issue, so far as of this writing, by adding to my sub-classed edit box functionality, to turn on scroll bars when it has focus and off when focus is lost. This seems to work fine.
>
>Can anyone think of why this approach would be wrong or limit something else?
As workarounds go, that sounds like a good one - try to precisely target the exact issue. I can't think of a way to get more precise than that.
My guess would be the root cause is an unusual sequence of events firing or controls being refreshed. The best solution would be to determine the cause, and fix that, rather than use a workaround. I think earlier on I suggested trying SET COVERAGE to get a log of events firing, for further analysis.
But, life goes on, at some point you have to say enough is enough and ship the code. Or more formally, determine the cost/benefit ratio of further analysis :)
Regards. Al
"Violence is the last refuge of the incompetent." -- Isaac Asimov
"Never let your sense of morals prevent you from doing what is right." -- Isaac Asimov
Neither a despot, nor a doormat, be
Every app wants to be a database app when it grows up