So here's a strange one. I dim a recordset (rst) and open it against a table
in my temp database, simple enough. No problem. But when I issue a rst.find
command, it returns rst.eof, meaning it didn't find the key. Well the key is
there, no question. I try "trim", that doesn't affect the rst.find result.

Finally, I check the status of rst.Filter property. Sure enough, it reports
"0". Well, I figure I'm an idiot, and I must have set it...nope. Never set.
Came from the factory that way....

So, I proceed to set it to "" before every rst.find, and all is well.

Any ideas where that crazy filter came from? ADO Bug?
--
Jim

hi Jim,

On 21.01.2010 16:03, JimS wrote:
> Any ideas where that crazy filter came from? ADO Bug?
It's not easy to guess without a concise and complete example... can you
provide one?


mfG
--> stefan <--

From the typelib: adFilterNone = 0

So this basicly means "no filter", the way they come from the factory...

cheers,
</wqw>

"JimS" wrote:

> So here's a strange one. I dim a recordset (rst) and open it against a table
> in my temp database, simple enough. No problem. But when I issue a rst.find
> command, it returns rst.eof, meaning it didn't find the key. Well the key is
> there, no question. I try "trim", that doesn't affect the rst.find result.
>
> Finally, I check the status of rst.Filter property. Sure enough, it reports
> "0". Well, I figure I'm an idiot, and I must have set it...nope. Never set.
> Came from the factory that way....
>
> So, I proceed to set it to "" before every rst.find, and all is well.
>
> Any ideas where that crazy filter came from? ADO Bug?
> --
> Jim