Re: ORA-01405: fetched column value is NULL

In article <3hks8d$9of_at_cs3.brookes.ac.uk>, p0070621_at_brookes.ac.uk (Tommy Wareing) writes:
|> In article <170sysD3qp7q.GqA_at_netcom.com>, 170 Systems says...
|> >Since the program worked in v6 without checking for nulls, I would guess
|> >that you could get by by just declaring the indicator variables and
|> >referencing them in the INTO clauses.
|>
|> The diagnosis is correct: I read it in one of the books, although I've
|> never used v7 (we're moving to it in a couple of weeks).
|>
|> I believe there's a command line option to the pre-compiler which makes
|> it behave in the same way as it did under v6 (RDBMS=6?).

Yes - the option is DBMS=V6. Note that the 1.5 Precompiler manuals INCORRECTLY state that you can use MODE=ORACLE to avoid the ORA-1405 error. This is true, but you also need DBMS=V6. This has been corrected in the 1.6 manuals.  

|> --
|> _________________________ __________________________________________
|> / Tommy Wareing \ / I've been looking for an original sin, \
|> | p0070621_at_brookes.ac.uk X One with a twist and a bit of a spin |
|> \ 0865-483389 / \ -- Pandora's Box, Jim Steinman /
|> ~~~~~~~~~~~~~~~~~~~~~~~~~ ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
|>
Received on Mon Feb 13 1995 - 03:26:11 CET