Will do.  Thanks.

Just add a test that if the WIdth is <= 0 then bail...there is nothing to render.

I added the Try-Catch block as Trent suggested.  The form is behaving better.  Since the try-catch block basically is doing nothing but bypassing the bad code, may I ask what is the code supposed to be doing?  Just trying to understand why things work the way they do.

Thanks!
Bill

What version are you using when you run the project?

I'm sorry, but I cannot reproduce this which means that it has already been addressed.  I am not sure if the most recently posted beta has this in it or not at this point, I will have to research when this was fixed, whic to be honest, I think was a while back.  But in any case, it would require an update of your assemblies.  Here would be my suggestion for your immediate resolution, just open the SF source, and in teh OnPaint, place a Try/Catch around the entire OnPaint.  We actually fixed this differently, but this will resolve your problem and get you going down your current path.

The next SF beta will be a bigger update because all of the BO partial classes will have to be rebuilt as the property type descriptors are different (for the better) now.  So in any case, you will probably just wnt to fix what you have since you are in the middle of testing (from what I gather).

Thanks, Ivan.  Not urgent, but the window is already well into the testing phase, so to restructure it would be a big task.  For now, the users have been instructed that the workaround is to simply not minimize that window.  Not the best workaround from a user standpoint, but knowing the Strataframe gurus, it will not be long before they have a fix prepared.

Hey Bill.

I tested over here and got the error. It looks like a problem with a the TabControl, when you Dock the SplitContainer to it. Without a TabControl, it works fine docked. With a TabControl, it works fine undocked. So, if it is urgent, you could try one of these scenarios.

Run the app, minimize the form, then restore the form.  The app fails on two different systems in our office, so I am not suspecting a local environment problem.  I'd rather not update to the beta unless I have to.  Are you unable to reproduce the behavior, still?

How do you reproduce the error with your sample?  It is not failing, so I am guessing that your assemblies are not up to date.  If I need to do something to force the error, then please let me know.  Thanks.

here's the sample