Carl Karsten wrote:
> I know I need to get PK's working, but wondering if this is something
> unexpected, espically the "for field 'Description'" part:
>
> [EMAIL PROTECTED]:~/dev/apps/op7/src/op7$ python op7.py
> '/usr/lib/python2.4/site-packages/dabo' not versioned, and not exported
> Dabo Info Log: Mon Dec 11 14:35:22 2006: 1 database connection definition(s)
> loaded.
> Dabo Info Log: Mon Dec 11 14:35:22 2006: User interface already set to 'wx',
> so
> dApp didn't touch it.
> Dabo Info Log: Mon Dec 11 14:35:22 2006: wxPython Version: 2.6.3.2 wxGTK
> (unicode) (gtk2)
> Dabo Error Log: Mon Dec 11 14:35:30 2006: Failed to create newval for field
> 'kAssetDescriptions_pk'
> Dabo Error Log: Mon Dec 11 14:35:30 2006: TYPES: {}
> Dabo Error Log: Mon Dec 11 14:35:30 2006: 'kAssetDescriptions_pk'
> Dabo Error Log: Mon Dec 11 14:35:30 2006: Failed to create newval for field
> 'Description'
> Dabo Error Log: Mon Dec 11 14:35:30 2006: TYPES: {}
> Dabo Error Log: Mon Dec 11 14:35:30 2006: 'Description'
You get this when adding a new record to a dabo cursor that doesn't yet
know its field types. It is usually no big deal, and you can get around
it by specifying a biz.DataStructure explicitly (I've been meaning to
put that into AppWizard, but it isn't there yet). In the case where you
add a new record and the field types can't be determined, they'll get
empty string values. We need to look at this and tighten it up.
--
pkm ~ http://paulmcnett.com
_______________________________________________
Post Messages to: [email protected]
Subscription Maintenance: http://leafe.com/mailman/listinfo/dabo-users
