>The VFP6 class browser is miles ahead of VFP5 for displaying type library information...

That is very welcome news! Can you specify in what way? Also, does VFP6 compile type library information for VFP6 COM objects in a manner more consistent with other MS tools like VB? For example, VFP5 COM objects don't list parameters that can be passed in methods in the type library. As a result, I have to specify the parameters in the description in order for them to show up in the type library. That's fine, but it makes it more difficult in using that object in other tools, especially those that support Intellisense. It also does not show what type of value should be specified for a property or a parameter, although that is most likely due to the lack of an "option explicit" feature for variable and property declaration. VFP is a great product, but for it to be used in a multi-tool strategy like what MS is pushing (with VFP focus at the middle tier) this information has to be available in the type library to make the overall solution more robust. Thanks for any insight you can provide. I hear folks at DevCon were excited about your class browser demos.