🚀 go-pugleaf

Ok,

Got it.
The ExecDirect is covering up the error, but only because the SQLMoreResults 
needs to be called to get passed the output of the first line which does 
nothing.
More results then returns the insert error the next time. So it is necessary 
to "walk" through the results of the query one result set at a time.

That is what seems logical in 20/20 hind sight.

Thanks.
V.


"Valence" <valence.crearer@Itron.com> wrote in message 
news:465b1803$1@newsgroups.borland.com...
>I suspect this is something fundamental I'm missing:
>
> SQLExecDirect does not return an error for the following SQL:
> <snip>
> declare @test int
> set @test = 1
> raiserror('Test Error',16,1)
> <\snip>
>
> It seems that if the error occurs on the first line, then the error is 
> returned. If the error occurs after the first action, it is not. That is 
> to say that SQLGetDiagField tells me that there is no error as well as 
> SQLExecDirect returns SQL_SUCCESS.
>
> Any ideas?
> Thanks.
>