Originally Posted by
Soundhouse
...The problem is even when the user chooses the second choice of the same value, the user is sent to the 1st occurrence every time...
I didn't wade thru Allen's article, which is no doubt accurate (but can be daunting to newbies) but the standard approach for this kind of search is to use FindFirst...and that's exactly what it is doing. With two occurrences of 11771, it will always take you to the first Record where 11771 appears!
You have to have a unique Field to search for. The usual hack is to concatenate, in this case, the CER No and another Field that would make the Record unique, and search on that Field.
A basic example would be to concatenate a last name and Social Security Number. With six Smiths in the database, Access will always retrieve the first Smith it encounters, regardless of which Smith you select...but searching on Smith plus their SSN, which will create a unique Field, it'll retrieve the one selected.
Linq ;0)>
The problem with making anything foolproof...is that fools are so darn ingenious!
All posts/responses based on Access 2003/2007