The strange thing is that UsedRange returns the correct row count (160 rows)
so the ODBC driver is, apparently, not using UsedRange as documented.

Thank you for your input - using a WHERE clause sounds like a more elegant
workaround than what I proposed!

Tim