Hi all,

I'm having a problem where Sql sent to FM through ODBC is causing the
program sending the Sql to shutdown.

The query is:

SELECT *
FROM TABLE
WHERE ID = 235 OR ID = 256

It would seem simple, but its not. MS Query does something to the Sql
it sends before it sends it, so it seems to work (although entering
that exact sql to send in MS Query causes it to close as well).

Any ideas as to why such a simple thing would cause such problems?

Thanks
Andy

In article <1123161258.095439.112610 (AT) g14g2000cwa (DOT) googlegroups.com>,
ajohnstone (AT) capcitypress (DOT) com says...
Wasn't there just a thread about this? Something about using
parenthesis...

e.g.

WHERE ((ID=235) OR (ID=256))

Yes, that was my thread. I thought I fixed it, but using the ()s still
does not help.

Andy

I discovered something else... its not executing the Sql that is a
problem,
its moving to the last row. (I'm using C# IDataReader.Read().. the
Read actually is the line the program closes on).

Andy

In article <1123177964.552094.246390 (AT) o13g2000cwo (DOT) googlegroups.com>,
ajohnstone (AT) capcitypress (DOT) com says...
So... you've got the data in a datatable/dataset?

A datareader... I copy the data from the reader into my own objects.

The problem actually occurs at the point then the Read method should
return false, indicating that there are no more rows. Instead of
returning false, my application exits.

The odd thing is that i can hardcode a simple sql statement with an OR
clause, and that works.

The application builds a sql statement (which looks correct to me), but
sets the parameters using IDataParameter objects.

So either there is something wrong with the Sql, or there's a problem
when using parameters with an IDbCommand.

Andy