> I have a form with a subform in it, linked by an ID number,
> and I don't want the user to be able to go to a new record
> in the subform.  There should be only one record per
> subform.

> I already disabled all navigation buttons on the subform,
> so the only way that a user could still go to a new record
> is by pressing pagedown. I can't switch Allow Additions to
> NO, because I want there to be a new blank record in the
> subform when a new record is created in the main form. Do
> you see the problem here?

> If I set the Allow Additions property to NO on the main
> form, the subforms work properly, but then a new form
> cannot be created on the main form, which is not
> acceptable.

> Any solutions would be greatly appreciated.

> -Tim

>-----Original Message-----
>Try setting the Cycle Record property for the subform to
Current Record.


>> I have a form with a subform in it, linked by an ID
number,
>> and I don't want the user to be able to go to a new
record
>> in the subform.  There should be only one record per
>> subform.

>> I already disabled all navigation buttons on the
subform,
>> so the only way that a user could still go to a new
record
>> is by pressing pagedown. I can't switch Allow Additions
to
>> NO, because I want there to be a new blank record in the
>> subform when a new record is created in the main form.
Do
>> you see the problem here?

>> If I set the Allow Additions property to NO on the main
>> form, the subforms work properly, but then a new form
>> cannot be created on the main form, which is not
>> acceptable.

>> Any solutions would be greatly appreciated.

>> -Tim

>.

> The Cycle Record fixes the problem for tabbing, but not for
> page down and page up, unfortunately. Any other ideas?

> >-----Original Message-----
> >Try setting the Cycle Record property for the subform to
> Current Record.


> >> I have a form with a subform in it, linked by an ID
> number,
> >> and I don't want the user to be able to go to a new
> record
> >> in the subform.  There should be only one record per
> >> subform.

> >> I already disabled all navigation buttons on the
> subform,
> >> so the only way that a user could still go to a new
> record
> >> is by pressing pagedown. I can't switch Allow Additions
> to
> >> NO, because I want there to be a new blank record in the
> >> subform when a new record is created in the main form.
> Do
> >> you see the problem here?

> >> If I set the Allow Additions property to NO on the main
> >> form, the subforms work properly, but then a new form
> >> cannot be created on the main form, which is not
> >> acceptable.

> >> Any solutions would be greatly appreciated.

> >> -Tim

> >.

> No, I don't have a specific suggestion on this. There have been other
> postings about how you can "capture" a key action such as PageUp etc., but
> I've not tried one yet. Do search for KeyPress event.

> > The Cycle Record fixes the problem for tabbing, but not for
> > page down and page up, unfortunately. Any other ideas?

> > >-----Original Message-----
> > >Try setting the Cycle Record property for the subform to
> > Current Record.


> > >> I have a form with a subform in it, linked by an ID
> > number,
> > >> and I don't want the user to be able to go to a new
> > record
> > >> in the subform.  There should be only one record per
> > >> subform.

> > >> I already disabled all navigation buttons on the
> > subform,
> > >> so the only way that a user could still go to a new
> > record
> > >> is by pressing pagedown. I can't switch Allow Additions
> > to
> > >> NO, because I want there to be a new blank record in the
> > >> subform when a new record is created in the main form.
> > Do
> > >> you see the problem here?

> > >> If I set the Allow Additions property to NO on the main
> > >> form, the subforms work properly, but then a new form
> > >> cannot be created on the main form, which is not
> > >> acceptable.

> > >> Any solutions would be greatly appreciated.

> > >> -Tim

> > >.