On Form- A I have ComboBox-B with RowSource that selectes the records to be
displayed. the records consist of fields showing athletic events, skill
levels and age category for the event: Solo, Advanced, 10-12. This works
fine. when I select a record in ComboBox-B subform-S displays a recordset of
who competed in the Event, Level, and Age Group as selected in ComboBox-B.

the problem is that after the subform is populated the current record
selector in ComboBox-B changes to the selected event, level and youngest age
of that group. Then when I try to resort the records in the subform in a
different order (score, rank, or by name) I get the records with the youngest
age (0-6), not the record set I originally selected.

Why would the current record pointer change? I have looked for a refresh or
a requery in the module but there are none that get executed when the problem
happens. anyway I think a requery or refresh of ComboBox-B would cause the
pointer to reset at the top of the record set, not just move 4 or 5 records.

HELP

Steve S.

"Steve S" <(E-Mail Removed)> wrote in message
news:7A11F5E2-BAD9-492F-B913-(E-Mail Removed)
> On Form- A I have ComboBox-B with RowSource that selectes the records
> to be displayed. the records consist of fields showing athletic
> events, skill levels and age category for the event: Solo, Advanced,
> 10-12. This works fine. when I select a record in ComboBox-B
> subform-S displays a recordset of who competed in the Event, Level,
> and Age Group as selected in ComboBox-B.
>
> the problem is that after the subform is populated the current record
> selector in ComboBox-B changes to the selected event, level and
> youngest age of that group. Then when I try to resort the records
> in the subform in a different order (score, rank, or by name) I get
> the records with the youngest age (0-6), not the record set I
> originally selected.
>
> Why would the current record pointer change? I have looked for a
> refresh or a requery in the module but there are none that get
> executed when the problem happens. anyway I think a requery or
> refresh of ComboBox-B would cause the pointer to reset at the top of
> the record set, not just move 4 or 5 records.
>
> HELP
>
> Steve S.

Is the combo box bound to a field in the main form's RecordSource? What
code is there in the combo box's events?

--
Dirk Goldgar, MS Access MVP
www.datagnostics.com

(please reply to the newsgroup)

Your suggestion to look at the Bound Column solved the problem. I looked at
an older version of my db and changed the bound field from 0 to 1 and got the
exact same results as I had in the version with porblems. I changed it back
to 0 and everythibg worked fine.

I next opened the latest version and saw that the bound column was already
set to 0. I changed it to 1 and the problem stayed the same. Changed it
back to 0 and the problem went away. go figure. I had run repair several
times but that did not help.

thanks for your help

Steve

"Dirk Goldgar" wrote:

> "Steve S" <(E-Mail Removed)> wrote in message
> news:7A11F5E2-BAD9-492F-B913-(E-Mail Removed)
> > On Form- A I have ComboBox-B with RowSource that selectes the records
> > to be displayed. the records consist of fields showing athletic
> > events, skill levels and age category for the event: Solo, Advanced,
> > 10-12. This works fine. when I select a record in ComboBox-B
> > subform-S displays a recordset of who competed in the Event, Level,
> > and Age Group as selected in ComboBox-B.
> >
> > the problem is that after the subform is populated the current record
> > selector in ComboBox-B changes to the selected event, level and
> > youngest age of that group. Then when I try to resort the records
> > in the subform in a different order (score, rank, or by name) I get
> > the records with the youngest age (0-6), not the record set I
> > originally selected.
> >
> > Why would the current record pointer change? I have looked for a
> > refresh or a requery in the module but there are none that get
> > executed when the problem happens. anyway I think a requery or
> > refresh of ComboBox-B would cause the pointer to reset at the top of
> > the record set, not just move 4 or 5 records.
> >
> > HELP
> >
> > Steve S.
>
> Is the combo box bound to a field in the main form's RecordSource? What
> code is there in the combo box's events?
>
> --
> Dirk Goldgar, MS Access MVP
> www.datagnostics.com
>
> (please reply to the newsgroup)
>
>
>

"Steve S" <(E-Mail Removed)> wrote in message
news:354E2930-E357-4E52-A4A4-(E-Mail Removed)
> Your suggestion to look at the Bound Column solved the problem. I
> looked at an older version of my db and changed the bound field from
> 0 to 1 and got the exact same results as I had in the version with
> porblems. I changed it back to 0 and everythibg worked fine.
>
> I next opened the latest version and saw that the bound column was
> already set to 0. I changed it to 1 and the problem stayed the same.
> Changed it back to 0 and the problem went away. go figure. I had
> run repair several times but that did not help.
>
> thanks for your help

Now *I'm* as mystified as you were, but if it's fixed, I guess all is
well. You're welcome, for whatever help I was.

--
Dirk Goldgar, MS Access MVP
www.datagnostics.com

(please reply to the newsgroup)