I have the exact same problem (see my post ODBC and Data controls). I wonder
if this only happens with Data Controls. Anyway, if you set the option to 64
(SQL_PASSTHROUGH), this might work but this is not the solution you want
because SQL_PASSTHROUGH automatically makes the data control read-only and you
can't do things like FIND, EDIT, UPDATE.

Please post any answers you get. I'll do the same with mine.

writes:

using:

This is a follow-up to my earlier reply. I think I may have discovered the
problem. In our case, a public synonym defined for the underlying table was
causing the problem. Note that the error "Couldn't find input table or query
..." is a different error message from "Table or view does not exist". The
latter error can be invoked if you intentionally mispell the table name. This
is correct because the table does not exist. However, in the "couldn't find
input table..." error, the table *does* exist but ownership or reference to
it is kind of vague, thus it couldn't be found.

Our problem was corrected by removing the public synonym defined for the
underlying table.

Hope this helps.