Ken Dibble wrote:
>> Your select statement must provide "all" the fields that are part of the
>> bizobj you defined. So:
>> addField("field1")
>> addField("field2")
>>
>> Your SQL statement must provide field2 and field2.
>>
>> So the error is tell you that 'musRecs.pkid' is missing from your select
>> statement.
>
> First of all, it's quite possible in a situation like this to involve two
> or more fields with the same name from two or more different tables in a
> complex query. How can the bizobj handle that?
>
> Second, I'm pretty sure Ed said that I can either use bizobj stuff like
> addField() and setWhereClause(), OR use UserSQL, but not both.
>
> Ken
>
>
If i recall correctly dabo isn't involved in where the fields came from.
Dabo doesn't know about the tablestructure, it only sees the resultset.
So you might try using fieldaliases and tell the bizobj the names of
your resulting aliases.
eg.: addfield("alias1")...
Best would be to run your query directly against the dbapi or take a
look at the outcome of the actual execute() call.
If you are able to look at the description of the resultset, you might
know if there is a keyfield.
I don't know if the implementation of aliases is foolproof as someone
had problems with them. But i think this was for a postgres db.
Other will correct me or give better hints on that.
Uwe
_______________________________________________
Post Messages to: [email protected]
Subscription Maintenance: http://leafe.com/mailman/listinfo/dabo-users
