Ah..as you can see..we always want to "compile" our code before we try and
run it...
So, our code in running on a form, and in that form we have a listbox. Are
you sure of the name of the listbox?
Or is that listbox in the other form?
Remember, a text box control, or listbox does NOT need to be the same name
as the underlying field, or data set (and, in your case..it is not clear if
the listbox is un-bound).
Often, a lot of developers will ALWAYS use separate names from the field
names. So, you can place a text box on a screen called:
txtLastName
But, in fact, the above control is bound to a field called LastName. So,
control names, and what fields they are bound do not have to be the same
(but often are).
So, did you double check the name of the listbox you have on the
form...(while looking at the from, flip it into design mode..and click once
on the listbox.....is the name the same as what you have in code?
And, if that listbox is on another form then where the code is running, the
obviously, you have to qualify the forms name and tell he code what form you
are to find this info..
rst.FindFirst "SubscriberID ="& forms!YourFormNaameGoesHere!SelectInfo
As mentioned, you only need forms!YourFormNameGoesHere if the control you
are using in code is not on the same form as the code.
Also, if subscriberID is a text value, then you need to surround the
condition with quotes...(but lets get the code compiling first..BEFORE we
even try to run the code...). Once we get the code compiled..then we can
start the debugging process...