Problem with dynamic filtering

[Guest]

I have a master/subform, where a text field on the master form filters the
records viewed via the subform.

Problem:

This works fine (i.e. enter "a" in the text field, and only records with an
"a" in the relevant field are listed for the subform), UNTIL you enter an
invalid filter string, i.e. when the result set is zero records.

(The subform is set to not allow new records to be created). Instead of just
showing an empty form, the application fails, blowing up with the error "You
can't go to the specified record".

At this point I can't readily recover from the error, I can't reset the
filter string, because Access thinks the form is empty, so there's no text
box to set properties on!

Any ideas how I can allow the user to interactively filter a record set, but
trap the "no records found" case BEFORE the subform blows up?

Regards: Colin

 

[Rob Oldfield]

On your other post, the text box was on the main form. That is where it
needs to be.

 

[Guest]

On your other post, the text box was on the main form. That is where it
needs to be.

That may be true. However that doesn't alter the basic problem. When the
filter results in no records being selected, the form/script combo blows up.
I need a way to either trap the problem before it occurs, or recover from it.

With the problem as it is, i can't even store the previous filter string and
reload it in case of an error, because by the time I hit the error the
control is gone and I can't reset it's value.

 

[Rob Oldfield]

That may be true. However that doesn't alter the basic problem. When the
filter results in no records being selected, the form/script combo blows up.
I need a way to either trap the problem before it occurs, or recover from it.

With the problem as it is, i can't even store the previous filter string and
reload it in case of an error, because by the time I hit the error the
control is gone and I can't reset it's value.

Dirk has the problem nailed in his response in the other thread. For
reference, starting two threads on the same topic is not a good idea. It
can end up with two separate versions of the same conversation going at the
same time.

 

[Guest]

I Was trying to follow proper etiquette by not asking two quite different
questions (one about bizarre text box selections, one about null recordsets)
in one post, although both issues occur in the same form.

However you are right in saying Dirk's response almost certainly nails the
source of the text selection problem.

I'm still struggling with how to deal with the empty recordset problem,
however at you suggestion I will continue that discussion in the other
thread. Thanks for your help so far.

Regards:Colin

 

[Rob Oldfield]

The problem won't occur if the control is on the main form.