On Mar 3, 2007, at 4:05 PM, Ken Dibble wrote:
>> No, but you do need to include that KeyField in the UserSQL
>> statement.
>
> The KeyField *is* in the query.
Yes, but not with the table.column format. You want to specify the
column that pertains to the key field.
>> I've never tried running a bizobj without a DataSource. What
>> happensif you set this to the name of the table?
>
> There are four tables involved in the query; which one would I use?
Is there a 'main' table in the query? The one that would be updated,
if you were writing this for updates?
>> This should always be just a column name, not a
>> table.column name.
>
> All of my tables have a pkid field; how does Dabo know which one I'm
> talking about?
There can only be one 'pkid' in the data set.
> In any case, I tried it that way; same error.
Here was the error you reported:
File "C:\Program Files\Dabo Runtime\dabo\db\dCursorMixin.py",
line 1362,
in _getRecordByPk
KeyError: 'musRecs.pkid'
This means that there was no column in the dataset with the key
value of 'musRecs.pkid'. You're saying that if you change the
KeyField to just 'pkid', you still get an error saying that you have
no key named 'pkid'? If so, then you don't have that name in your
result set. I don't know why, but that's what a KeyError means.
-- Ed Leafe
-- http://leafe.com
-- http://dabodev.com
_______________________________________________
Post Messages to: [email protected]
Subscription Maintenance: http://leafe.com/mailman/listinfo/dabo-users
