>Mike,
>
>We'll continue to experiment. I agree with you that we may be left with holes that can't or shouldn't be closed. Example: the fll. PHDBase will be a loss but IMHO converting to NET represents an opportunity to replace lots of VFP-isms with managed code. yes that is making a virtue of a necessity(!) but it's also true. Which is why I've reviewed my suggestion about using VFP to create binaries for stuff like Blowfish. That would be fun, but one of the benefits of joining the IL world is that somebody else has done it already in C# over 1000 times ;-) with their work immediately available without the historic uncertainty for VFPers contemplating 3rd party ActiveX or dll. So rather than reinventing that particular wheel I think I'll start a mini-group investigating NET encryption options so we can deliver a recommended approach for people converting their VFP projects into eT scripts.
>
>There are other holes too, but the February release is almost upon us with lots of new functionality so I'll refrain from commenting till then.

John,
When are you eligible to receive the eT Lifetime Achievement Award?