question about the notorious "row not found"

Hi everybody,
at present we are trying to evaluate SAPDB with one of our projects,
which is currently using postgres. Access is via ODBC.
We downloaded the binaries for Solaris32 and installed etc.
After having gotten x_server etc. to run we tried to start our
programm and found the following things:
1) where clauses which evaluate to false will (in some cases? all of
   our's anyway ;-( ) return "error 100" for the statement.
   So far, so bad. This *_could_* be handled by our app.
2) If one of those statements is part of a nested statement, say, you
   have a "select from a join comprising of data from two selects",
   and one of those subselects has found nothing, the whole statement
   will fail with "not an sql statement", "<somthing> expected" etc.

Can this (esp. 2.) be avoided somehow? Are we doing something wrong here?

N.B.: Switching the SQLMode (via driver-setup) from INTERNAL to ANSI,
      DB2 or ORACLE only seems to make things worse.

P.S.: Any general statement is like a cheque drawn on a bank. Its value
      depends on what is there to meet it.
        - Ezra Pound (1885-1972), ABC of Reading, 1934

-- 
Hartmut "Hardy" Raschick / Dept. RD41
ke Kommunikations-Elektronik GmbH
Wohlenberstr. 3, 30179 Hannover
Phone: ++49 (0)511 6747-564
Fax: ++49 (0)511 6747-340
e-Mail: [email protected]
http://www.ke-elektronik.de