Having a field name and a table the same name should not be a problem.

I still fail to recognize the potency of your problem. Is it possible you
can send me a sample application demonstrating the problem and clear simple
instructions on how to reproduce it?

Thanks,
Jason Wharton

----- Original Message -----
From: "Riho-Rene Ellermaa" <r.ellermaa@...>
To: <IBObjects@yahoogroups.com>
Sent: Wednesday, October 08, 2003 12:18 AM
Subject: RE: [IBO] RE: Datapump action


> > -----Original Message-----
> > From: Jason Wharton [mailto:jwharton@...]
> > Sent: Wednesday, October 08, 2003 1:24 AM
> > To: IBObjects@yahoogroups.com
> > Subject: Re: [IBO] RE: Datapump action
> >
> >
> > Is one of them a NOT NULL column and the other NULLABLE?
> >
> > Jason
>
> Some of the fields are NOT NULL and some are NULLABLE. ACCOUNT is NOT
NULL.
> I checked the values of all fields in AfterFetchRow. All other fields
(both kind) had DstRow values as NULL and ARow contained the values.
> Only ACCOUNT had the opposite.
>
> It looks like ACCOUNT already pumped its value to DstRow, but why set the
ARow value to NULL?
>
> I use TIB_Cursors for Pump statements and the SQL was "SELECT * FROM
ACCOUNT" (I hope it's not confusing for IBO that I have the table name and
one field with the same name).
>
> CREATE TABLE ACCOUNT (
> ID INTEGER NOT NULL,
> BANK VARCHAR(15) CHARACTER SET WIN1252 NOT NULL,
> ACCOUNT VARCHAR(20) CHARACTER SET WIN1252 NOT NULL,
> OWNER VARCHAR(70) CHARACTER SET WIN1252,
> INSTALL VARCHAR(20) CHARACTER SET WIN1252 NOT NULL,
> REGNO VARCHAR(20) CHARACTER SET WIN1252,
> PRIMARY KEY (ID)
> );
>
>
> Riho-Rene Ellermaa
> senior programmer