New line in nested subform

[Hillary]

This is the nesting structure of the forms...

Main Form: Projects
Subform of Projects: PO
Subform of PO: PO Line (datasheet view)

When I enter data into PO Line, a new line item does not appear so I can not enter in any more than one record at a time. I have to either click on the next PO or the next Project to get a new line in PO Line.

This only occurs when I work from frmProjects - the problem does not occur when I work from frmPO and enter the PO Line from there.

This is my first database with a nested subform. Is there a setting I may be missing?

Thanks,

Hillary

 

[TheAceMan1]

How are ya Hillary . . .

If the underlying [blue]table relationships[/blue] follow your nesting and the subforms are linked with [blue]Master/Child Link[/blue] fields, then:

[blue]You can't enter data in a subform, without entering data in its parent form.[/blue]

See Ya! . . . . . .

 

[Hillary]

Both parent tables are populated and I can put data into the nested subform what I can't do is add multiple lines without getting out of one of the parent records and getting back in.

For example, [frmProject].[Project ID] = 1; [frmPO].[PO ID] = 05-001 and [frmPO].[Project ID] = 1; I can enter data into frmPO Line where [frmPO Line].[PO Line ID] = 100 and [frmPO Line].[Project ID] = 1 and [frmPO Line].[PO ID] = 05-001. Usually when one enters data into a (datasheet view) subform, the next line for data entry appears immediatly. In this case, the next line doesn't appear unless I change frmProject from ID 1 to ID 2 and back to frmProject ID 1, then the next line of frmPO Line is there.

However, if I open frmPO (not as a subform in frmProject but as a standalone), I can enter data into it's subform, frmPO Line without any problems.

When I created the database, I created frmPO Line then frmPO and added subform frmPO Line to frmPO. Lastly, I created frmProject and added subform frmPO (which contains frmPO Line), hence the nesting.

Thanks,

Hillary

 

[TheAceMan1]

Hillary . . .

A number of things come to mind, but still not sure what path to take to advise you (to many blanks).

Post back your [blue]table structure & relationships[/blue], and the [blue]fields use for Link Master/Child[/blue] properties.

See Ya! . . . . . .