[AccessD] Two levels up (or down) , twice removed

Stuart,

<<There's no need for an OnCurrent event if you set the source of the hidden
control to the PK 
of the recordset of its  parent form.>>

  Not sure I understand; the grandchild is related to the child subform, not
the parent. You need to do that on the grandchild to get the grandchild form
to sync properly to the child subform.

  It's the only way I know of putting both child and grandchild on a main
form.

Jim.

-----Original Message-----
From: accessd-bounces at databaseadvisors.com
[mailto:accessd-bounces at databaseadvisors.com] On Behalf Of Stuart McLachlan
Sent: Wednesday, February 03, 2010 4:18 PM
To: Access Developers discussion and problem solving
Subject: Re: [AccessD] Two levels up (or down) , twice removed

There's no need for an OnCurrent event if you set the source of the hidden
control to the PK 
of the recordset of its  parent form.

-- 
Stuart

On 3 Feb 2010 at 15:37, Jim Dettman wrote:
>   So I put a hidden control on the main form, child form linking is
normal,
> then place the grandchild form on the main form and use the hidden control
> as the master link.  Last piece is in the child forms OnCurrent event, I
> update the hidden control on the parent. 
> 

-- 
AccessD mailing list
AccessD at databaseadvisors.com
http://databaseadvisors.com/mailman/listinfo/accessd
Website: http://www.databaseadvisors.com