[V4MD2] (VField reference not assigned)

[Heinrich Ruoff]

thanks again Sean for your brilliant analysis.
I'm kind of relieved ;-)

guess for the moment its better for me to go back to 2.0.3
and forget about the SQL LIMIT functionality that is 
working in the beta version.

cheers
Heinrich



On 6/14/05, Sean Wilson <snw at paradise.net.nz> wrote:
> 
> >Cheers Sean!
> >You got ot - thats exactly the problem!
> 
> Excellent.
> 
> >But there is already my next problem with the examples :-(
> >everywhere where a field name is used I get an script error:
> >property not found
> >
> >e.g.: in SQL_way -> Bind.dir
> >Step 1 using function ProduceTableData()
> >f = table.field(j)
> >row[symbol("col" & j)] = f.name
> 
> I'm seeing the same problem. When I look in the debugger at the point the
> error is thrown, f (which I think should be an instance of VField) is
> instead a number like 73187688. It looks like obtaining a field ref from an
> instance of a table with f = table.field(j) is failing - this would appear
> to be a bug.
> Actually, something stranger is going on - my message window suggests that
> an instance of VField *is* created, but it the reference created doesn't
> appear to be assigned properly:
> * V4MD * : VTable.field() ...
> * V4MD * : VField.new() ...
> done
> done
> 
> So, it's not something you're doing wrong, but definitely something that
> one of the xtra developers needs to look into.
> 
> Cheers,
> -Sean.
> 
> 
> _______________________________________________
> Valentina-beta mailing list
> Valentina-beta at lists.macserve.net
> http://lists.macserve.net/mailman/listinfo/valentina-beta
>