I am getting a fatal error everytime I open the BO Mapper now.  I have been getting it more and more frequently, and now I get it everytime I try to open it.  I have just added a new table and need to link it to a BO, but can't because I can't get into the mapper.  I have attached a screenshot, but it doesn't show much.  One time a stack trace came up but it was covered by the error window and when I moved it the error window traced over and blanked out the text on the stack trace.  I think it said something about System.Drawing.  It almost seems like some sort of memory/threading error since when I bring up the screen some pieces of it seem to not be drawing all the way.  Notice in the screen shots you can see other windows "through" the mapper.  Please let me know something on this.  I'm kind of stuck and unable to continue development until I can work with the mapper.  Thanks.

Oh, and just worth pointing out here.  I was able to go to another machine with the same assemblies and bring up the BO Mapper perfectly.  It points to the same database and everything.  Not sure exactly what that tells us, but it almost seems to be isolated to my PC.

That is a very, very odd error.  For some reason, it seems that the SQL query is pushing a WM_PAINT message up the WndProc call sequence on a background thread.  The WaitOne means that the SQL Server client is pausing the main thread while the background thread does the processing, but I have no idea why it's trying to paint during that.  We can put a try/catch in the OnPaint to prevent an exception from being thrown, but other than that, all I know to do is check the thread context to make sure it's on the main thread before painting.

Here are the DLLs with the try/catch in the OnPaint.  Maybe this will allow you to use the BOMapper on your computer.