Dear Jason,

It has taken a while to track down this error on my part.

with an IB_Query

I used an AddSQLWhereClause
followed by a
ParamByName statement

thinking that I had read somewhere that calling ParamByName
automatically 'Prepares' the Query.

In this case it does not and caused the access violation.

I thought that you might like to know in case this is inconsistent or
this could be better error trapped.

Kind regards,

Francis Moore

--- In IBObjects@y..., "Jason Wharton" <jwharton@i...> wrote:
> This has to be a result of something unique to your situation of
which we
> know nothing from your message. If there was something wrong with
this code
> you have right here everyone would be claiming problems. I'm not
saying
> there isn't something somewhere that needs to be addressed, it just
isn't
> evident in your post.
>
> Thanks,
> Jason Wharton
> CPS - Mesa AZ
> http://www.ibobjects.com
>
>
> ----- Original Message -----
> From: <moorefg@n...>
> To: <IBObjects@y...>
> Sent: Wednesday, February 07, 2001 12:12 PM
> Subject: [IBO] EAccessViolation
>
>
> > I am getting errors from the enclosed procedure in IBA.Column.IMP
> >
> > procedure TIB_ColumnInteger.SetValue( const NewValue: integer);
> > begin
> > SysBeforeModify;
> > SysSetIsNull( false );
> > integer(FNewColumnBuffer^) := NewValue;
> > SysAfterModify;
> > end;
> >
> > Any help as to where to look for the problem would be appreciated.
> >
> > Francis Moore
> >
> >
> >
> >
> >