It is possible to create dataobjects that have data fields that aren't
related to any particular table or column. For example, I have a data
object with two fields, "max" and "min". When you look at the dataobject
properties in the Fields tab, min and max aren't associated with any
column or table. The SELECT clause is overridden with something like
"MAX(time), MIN(time)". So I can bind max and min to display fields,
eventhough they don't actually exist as a column in a table in the db.
[EMAIL PROTECTED] wrote:
>
> My question in a nutshell:
> What's better...3 simpler DOs with point & click binding. vs. 1 complex DO with
> manual binding?
>
> Cracking it open:
> I have a page that displays a Repeated. 3 columns in the repeated have the same
> domain. Therefore, the SQL for the Rpt requires joining to the same table three
> times. To pick the same table more than once in the FROM clause, I believe I
> have to use the SQL tab in the Properties dialog and override the default SQL.
> No problem, but then how can I bind the 3 columns to the corresponding display
> fields in the Repeated? i.e. how do I access the 3 columns via code to use them
> to do a setValue?
>
> Maybe the better way is to create 3DOs (each one does one join to the common
> table) via point & click, and then bind their data field to the corresponding
> display field on the Rpt.
>
> Advice from a performance perspective is also welcome.
>
> Thanks!
> Janet
_________________________________________________________________________
For help in using, subscribing, and unsubscribing to the discussion
forums, please go to: http://www.netdynamics.com/support/visitdevfor.html
For dire need help, email: [EMAIL PROTECTED]
