Intellisense is not designed to work at runtime.

As for scoping, remember that VB is not object oriented. You're getting data hiding in VFP, which creates better OOP applications.


>Folks,
>
>Nope. Intellisense @ runtime is obviously useless I think. I expect intellisense to work just like in VB. I want to use a single connection in the entire form or project for that matter. General declarations in VB makes every single variable (private or public) available in the entire form or project with intellisense poping up.
>
>What I am doing in VFP is that I was forced to create an object to handle the ado object making it handy:
>
>

>init of the form:
>This.oConn = CREATEOBJECT("ADODB.CONNECTION")
>This.oConn.Open("ADODB.CONNECTION")
>This.oConn.CursorLocation = 2
>

>and somewhere in the click event of a button or somewhere else:
>

>oRS = Thisform.oConn.Execute("SELECT blah...blah")
>IF !oRS.EOF()
>   oRS.MoveFirst
>   DO WHILE !oRS.EOF()
>       blah...blah...
>   ENDDO
>ENDIF
>

>and it works fine but without intellisense available.
>Typing This.oConn. should have intellisense anywhere in the form not only ADO but other activex.
>
>That make sense to me but I expect others may disagree.
>
>>Intellisense does not work in Runtime. If you think about it, it makes sense. How many end users are writing code?
>>
>>
>>>Craig,
>>>
>>>What am I missing here??
>>>
>>>In the INIT method of the form,
>>>

>>>LOCAL oObj AS ADODB.CONNECTION
>>>oObj.OPEN("bbfsdsn","sa","")
>>>oObj.CursorLocation = 2
>>>

>>>This one does not work at runtime although intellisense popups during development time and within init only. Meaning, oObj. has no more intellisense popup in other methods.
>>>

>>>oObj = CREATEOBJECT("ADODB.CONNECTION")
>>>oObj.OPEN("bbfsdsn","sa","")
>>>oObj.CursorLocation = 2
>>>

>>>This one works, but no intellisense available in any method.
>>>
>>>Please educate me.