Hi George,

>AFAIK, for Intellisense to work across multiple environments it would have to heavily utilize Windows messaging services. Further, given the component design direction currently being utilized, it doesn't make much sense to me that they would build in this feature independently of its implementation elsewheres.

Actually, I tend to disagree here. First of all, the VFP 7 Intellisense bases on DBF files, that means it is native to VFP. Also, at one point during the demo, the debugger came up and what was in the code window really looked like CEE, except that the object had a different name.

Taking this into account and looking at the possibilities that are available in VFP and the VFP API, all we need is a hook to capture every single key stroke instead of just reacting on the SpaceBar or something like this, and we are practically done. Reading the current line in the editor window is easy, displaying a listbox at the current cursor position is not difficult either, neither is displaying a tooltip. And what else is needed to implement IntelliSense? Quering the code for some key words, analyizing the class hierarchy, obtaining information from ActiveX controls and OLE servers via the type library... All of this can easily be done within the current design of VFP.

Christof