Sue_H - Friday, January 20, 2017 3:32 PM
Hi Sue, I had similar thoughts this was a ADO recordset issue but it doesn't occur with Access and didn't occur for this client with this same piece of code until recently so I didn't want to rewrite the code if the problem exists in some ADO driver that only allows a limited number of record sets to be returned. What's strange is that this code doesn't fail with 1 in the record set, just 2 or more so the movenext should fail with 1 too. I'm not that familiar with this forum so if you know of a more focused post area let me know.