Bryan,
The debugger in VFP6 can not drill down into the properties of a COM object until the property has been accessed from some code.
The debugger was made smarter in VFP7 and beyond. So do all your development work in VFP7 and then just test it back in 6, but you won't have the same debugging facilities in 6.
>I am trying to develop a mapping application in both VFP 6.0 and VFP 7.0. In VFP 7.0, when I issue the command "loAdoConn = CREATEOBJECT('ADODB.Connection')" and expand the resulting object in the Watch Window of the debugger I can see all the properties for the loAdoConn ADO Object. When I issue the same command in VFP 6.0, there are no properties at all for the loAdoConn ADO Object. Can anyone tell me why?