Table of a VFeld from a VCursor

[Ed Kleban]

Makes sense.  However my question still remains:

>>> I'm hoping that given you have a VField obtained from a VCursor in this
>>> manner that there is some way to determine which VCursor the VField
>>> comes
>>> from.  Is there some way to find out?

Is there a way to find out from a VField what it's VCursor is, or to as a
VCursor what it's VFields are or whether a given VField  belongs to it?
Any unorthodox, implementation-dependent, dangerous "cheats" that might
accomplish this?



On 11/21/05 12:02 PM, "Ruslan Zasukhin" <sunshine at public.kherson.ua> wrote:

> On 11/21/05 7:51 PM, "Charles Yeomans" <yeomans at desuetude.com> wrote:
> 
>>> When you get a VField from a VCursor, such as with:
>>> 
>>>     aVField = aVCursor.Field( "SomeFieldName" )
>>> 
>>> What is the value of aVField.Table ?
>>> 
>>>     Is it nil?
>>>     Is it aVCursor?
>>>     Is it the VTable from which the vField was extracted by SQL and
>>> added to
>>> the Cursor?
>>> 
>>> I'm hoping that given you have a VField obtained from a VCursor in this
>>> manner that there is some way to determine which VCursor the VField
>>> comes
>>> from.  Is there some way to find out?
>> 
>> I'm not sure that VField.Table makes sense here.  A cursor can be
>> thought of as a new, temporary table, and its fields are fields of this
>> temporary table.
> 
> Absolutely right.