Okay, it seems to work in .NET 1.1, but not in .NET 2.0. :wtf: Apparently .NET 2.0 has said, "The hell with security." One can easily run any code in a trusted zone without any regard whatsoever to standing individual assembly security requirements set by StrongNameIdentityPermission. :mad: -- I've killed again, haven't I?

Ah. Not calling base.OnRenderToolStripBorder(e) in the custom ToolStripRenderer seems to get rid of that nasty bordery aftertaste. Yay me. -- I've killed again, haven't I?

Yeah, I realized that after I posted it. A commerical for Buffy reruns came on about a half-hour later! RageInTheMachine9532 "...a pungent, ghastly, stinky piece of cheese!" -- The Roaming Gnome

Thanks for all the suggestions, everyone. Since I can access SQLite with just a slight modification to my overall design scheme, I'm going to use the wrapper to get this first iteration out. After that, I'll weigh these alternate DB solutions. -- I've killed again, haven't I?

Wow. I forgot I had an old dual 500-MHz machine here. I changed the progress update frequency on both applications, then took this test to it. I had to bump the test up to 100,000,000 iterations to tell the difference! The peek-and-pump program took 47.6 seconds, and the threaded program took 46.8. You guys are awesome. I officially unfurl my brow at the worker thread. :laugh: Thanks, [gb] -- I've killed again, haven't I? -- modified at 15:29 Wednesday 21st December, 2005