Hi,

>>this.IsInDesignMode
>
>I'll have to look into that. It is more readable.

And, IIRC, under the hood does exactly the same thing (i.e. the compiled code is a call to the method anyway)

>>>Are you doing much with WPF
>
>All my interface code is now being done in WPF. My non LOB DP stuff is still all in VFP and runs either as COM objects or as independent apps. (My LOB stuff is being moved to Linq to SQL)

> I'm adding some stuff to an ASP.NET site at the moment and using Linq to Sql for simple data access even though there is a traditional 'dataset' type layer in place for the existing pages. I love the simple, small amount of code required to pull in an object collection. But I'm reading that there will be no additional stuff added to Linq to Sql and that the Entity Framework is the preferred future option.....

> I just finished roughing out an IPC module that allows my VFP and WPF apps to communicate. WPF has a huge learning curve, but it allows me easily do some of the things that I wanted to do in VFP that required massive coding to accomplish. The parent child relationship between objects also gives me a nice warm and fuzzy feeling as it reminds me a bit of VFP.
>
>Overall I'm really liking WPF. I'm using it to take all my applications and sew them together into one cohesive interface. As I mentioned the learning curve is a b***ch, but once you get it down it's very powerful.

I'm still hoping to get back to full time WPF soon (but have been hoping for over a year now). In some ways the delay is good - I've a much clearer idea now of how everything fits together. If I had started a year ago large parts of the app would probably have been a mess.

>Today I'm trying to track down a @#$%$@#% memory leak. That didn't happen too often in VFP.
Saw you cracked that one :-}

Regards,
Viv