Just a little problem I have a long time with the ADO Dataset Iterator that time didn't let me complain about that. When a query returns no row it complains about BOF or EOF being true, I had to ignore failure in actions that may return no records but this trapped me yesterday, when my ADO dataset iterator was supposed to expose a real error.
I think this shouldn't be an error just as 0 files found in file iterator isn't an error.
You’re right, this is a bug. The iterator doesn’t always fail if no rows are found, but it does do it sometimes. I’ve fixed the bug, the fix will be available in the next test build. Just for completeness’ sake, I’ve added a new feature called “Fail if no rows are found”, although it defaults to off.
I’ll let you know when a test build with the fix is available.