On Saturday 03 March 2007 13:08, 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
"First of all" don't get upset!
I miss read your select statement - you are returning the "musRecs.pkid'.
OK so you are not using addField() within the bizobj only the UserSQL. I
thought at one time you were using addField().
So for now I would add 'as' in the select statement.
"musRecs.pkid as pkid" - I'll assume the form has a textbox with a DataField
= 'pkid'.
How can the bizobj use the same field name from different tables? Right now I
have a few pretty wild SQL statements I'm using that include several tables.
I'm using the "as" to get this done. It never occurred to me that Dabo
should do anything. But in the VFP world it would be handle by adding "_a"
etc...
What do others think? Should Dabo handle the issue? Is there something in
Dabo already?
--
John Fabiani
_______________________________________________
Post Messages to: [email protected]
Subscription Maintenance: http://leafe.com/mailman/listinfo/dabo-users
