Actually I would do this a different way, First I would not create a Master - Sub form form, as this does not accurately reflect a 1 to 1 relation, rather a 1 to 0 ..1 relation.
Rather create a form with 2 master level dataform controls. Now you must take over the task of handling updates to the two tables as a single transaction. This is a mandatory step if you are actually to have a 1 to 1 relationship You really have to choices on how to address this. 1 ) use the built in data navigation control and use your macros to catch the events on the dataform controls and work with the other tables data, via the other dataform control, appropriately. 2 ) do not use the built in data navigation bars at all - rather use a groug of your own buttons and some macro code to pre emptively move the record pointers ( using the dataform controls ) and handling posting data to the tables ( using the dataform controls, or separate prepared statements perhaps ) I would recommend the first approach, as this allows your form to better take advantage of the other built in features of Base - form based filtering, for example - in a much more efficient fashion. Drew On Tue, Feb 12, 2008 at 1:03 AM, Christian Ledermann < [EMAIL PROTECTED]> wrote: > I have two tables with a one to one relationship. > I created a form with a subform displaying the fields. > when I enter new data the data in the parent form gets saved > but the data in the subform is lost. > > The navigation bar in the main form does not allow me to save > when i change values in the subform (i.e. is greyed out). > > Is there a quick solution to this problem (without adding an extra > navigationbar to the subform - that obviously works )? > > ch > > > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] > >
