Form & Sub-Form

[jldum]

Hi there,

I am trying further ...
I created
a Form on [parent] table
a Form on [Children] table
a relation between parent & children
I then entered the [Children] form into the [parent] form
but when I scroll the parent , the children do not move in sync (actually do not move)

I created a List on [parent]
associated in drill-down mode the form on [children], this works OK

what are/is the option(s) when looking at form / sub-form relation ?
Awaiting reaction
Regards

JL D

[admin]

Hi JL,

I've made a fast'n'ugly example for you where I insert a related list on a form.. The trick is to scroll to the bottom of the drop down box and pick the related version of the report.
http://support.dynamicai.com/images/screenshots/boa/Rel_form_2010-02-08_1449.swf

I hope I din not misunderstand your question.

Best regards,

Bo

[jldum]

Hi Bo,
thanks,
need to review it , going quite fast.
I'll come back on it later.
regards
JL D

[jldum]

Hi Bo,

had several look at the sequence you produced and I reproduced it .
I noticed that when you produce a report-list the first column gives you access to a form when set in the general parameters.
1.
when the report-list is used in a form as a sub-form, this column is not longer available.
Any idea why? this would have allowed to look at the details of a row.
2.
navigating when records exists is OK
when you are in data entry mode, is there any easy to automate the generation of the FK in the sub-form or should we advise users to enter the relation manually ?

As I consider Data Entry capabilities as a Differentiator, I would appreciate to get exposed to the current limitations of this functionality and the best practices

Awaiting your reaction
regards
JL D

[admin]

Hi Jl,

1)
The usual scenario we see is having a detail (editable) list on a form. This is because we assume there is a one to many relationship between the master and the detail, what is your usage case? With the updatable and related detail list on the form, you can do things like maintain contact names by customer, order details by order etc. I'd be happy to setup an example and show you how this works.

2)
Currently we do not read the foreign keys from the database - I would not be surprised if we'll do that in a future release, but currently you must specify the relation yourself - but note that there's an option to match on fieldname automatically once the source(s) has been defined.

Best regards

Bo