I am converting a DBISAM application to ElevateDB.

I have a table TEST:

CREATE TABLE "Test"
(
"ID" INTEGER GENERATED BY DEFAULT AS IDENTITY (START WITH 46, INCREMENT BY 1) NOT NULL,
"Name" VARCHAR(24) COLLATE "ANSI_CI" NOT NULL,
"SequenceNo" INTEGER NOT NULL,
"Abbreviation" VARCHAR(12) COLLATE "ANSI" NOT NULL,
. . . . . . . . .
)

This table is displayed in a grid.  After performing some actions, all the values in the NAME column disappear.  The values become empty strings.  All the other columns are OK.  If I add
another column called NAMEX and populate it with the same values as the NAME column, then these values are always displayed.


Is there a problem giving a column a name of NAME?


--
Richard Harding
Windella Computer Knowhow
28 Freeman Drive
Lochinvar NSW 2321
Phone:    61 2 4930 7336
Mobile:    0419 016 032
email:    rharding@wck.com.au

Richard


Are you saying that the values in NAME are still there just not visible or that you have to re-type the values in NAMEX?

Roy Lambert

Richard,

What "actions" are you performing? You state that they are there and
showing but then "...after performing some actions" they are no longer
showing. Seems to me this might be the key to why they are no longer
there. Are you performing those same actions on the NAMEX field? Can
you advise as to the code or the actions?

--
Regards,
Jan Ferguson


Richard Harding wrote:

<<I am converting a DBISAM application to ElevateDB.
<<
<<I have a table TEST:
<<
<<CREATE TABLE "Test"
<<(
<<"ID" INTEGER GENERATED BY DEFAULT AS IDENTITY (START WITH 46,
<<INCREMENT BY 1) NOT NULL, "Name" VARCHAR(24) COLLATE "ANSI_CI" NOT
<<NULL, "SequenceNo" INTEGER NOT NULL,
<<"Abbreviation" VARCHAR(12) COLLATE "ANSI" NOT NULL,
<< . . . . . . . . .
<<)
<<
<<This table is displayed in a grid.  After performing some actions,
<<all the values in the NAME column disappear.  The values become empty
<<strings.  All the other columns are OK.  If I add another column
<<called NAMEX and populate it with the same values as the NAME column,
<<then these values are always displayed.
<<
<<
<<Is there a problem giving a column a name of NAME?
<<
<<
<<--
<<Richard Harding
<<Windella Computer Knowhow
<<28 Freeman Drive
<<Lochinvar NSW 2321
<<Phone:    61 2 4930 7336
<<Mobile:    0419 016 032
<<email:    rharding@wck.com.au
>>

Richard

Thank you Roy & Jan.

The values are still in the database.  However, after a RBUILDER report is run, the values of **Test.FieldByName('Name').AsString** is an empty string.  All the NAMES in the DBGRID are
now empty whilst all the other columns are OK.  (Including a newly created NAMEX column that has been populated with the values of NAME)

The original DBISAM table is:

/* SQL-92 Table Creation Script with DBISAM Extensions */

CREATE TABLE IF NOT EXISTS "Test"
(
  "ID" AUTOINC NOT NULL,
  "Name" VARCHAR(24) NOT NULL,
  "SequenceNo" INTEGER NOT NULL,
  "Abbreviation" VARCHAR(12) NOT NULL,
. . . . . . . . . .
PRIMARY KEY ("ID") COMPRESS FULL
LOCALE CODE 0
);

CREATE UNIQUE NOCASE INDEX IF NOT EXISTS "tsNameIND" ON "Test" ("Name") COMPRESS FULL;
CREATE UNIQUE NOCASE INDEX IF NOT EXISTS "tsSequenceIND" ON "Test" ("SequenceNo") COMPRESS FULL;

Importing the table into ElevateDB results in:
  
CREATE TABLE "Test"
(
"ID" INTEGER GENERATED BY DEFAULT AS IDENTITY (START WITH 51, INCREMENT BY 1) NOT NULL,
"Name" VARCHAR(24) COLLATE "ANSI_CI" NOT NULL,
"SequenceNo" INTEGER NOT NULL,
"Abbreviation" VARCHAR(12) COLLATE "ANSI" NOT NULL,
. . . . . . . . . . .
CONSTRAINT "PrimaryKey" PRIMARY KEY ("ID"),
CONSTRAINT "tsNameIND" UNIQUE ("Name"),
CONSTRAINT "tsSequenceIND" UNIQUE ("SequenceNo")
)


The indexes that existed in the DBISAM DB have been transformed into constraints in the ELEVATEDB DB.



--
Richard Harding
Windella Computer Knowhow
28 Freeman Drive
Lochinvar NSW 2321
Phone:   61 2 4930 7336
Mobile:   0419 016 032
email:   rharding@wck.com.au

Richard,

<< The values are still in the database.  However, after a RBUILDER report
is run, the values of **Test.FieldByName('Name').AsString** is an empty
string.  All the NAMES in the DBGRID are
> now empty whilst all the other columns are OK.  (Including a newly created
> NAMEX column that has been populated with the values of NAME) >>

Is "Test" a TEDBTable component or a TEDBQuery component ?

--
Tim Young
Elevate Software
www.elevatesoft.com

Hi Tim

>>>Is "Test" a TEDBTable component or a TEDBQuery component ?

Test is a TEDBTable component

--

Richard Harding
Windella Computer Knowhow
28 Freeman Drive
Lochinvar NSW 2321
Phone:   61 2 4930 7336
Mobile:   0419 016 032
email:   rharding@wck.com.au

Richard,

<< Test is a TEDBTable component >>

Could you send me an example of this ?  I'm not sure what is going on, but
it sounds like either EDB is getting seriously confused internally or
there's an invalid TField reference at the TDataSet level.

--
Tim Young
Elevate Software
www.elevatesoft.com

Tim,

Performing a lookup on the Test table is causing the NAME column values to disappear.  It is reproducable.

For example,

  TestID := dmData.taTest.Lookup('Name', TestName, 'ID');

I have attached a small project with a backup of an sample 2 table ElevateDB database (and the SQL to create the DB)


--
Richard Harding
Windella Computer Knowhow
28 Freeman Drive
Lochinvar NSW 2321
Phone:    61 2 4930 7336
Mobile:    0419 016 032
email:    rharding@wck.com.au

Richard,

<< I have attached a small project with a backup of an sample 2 table
ElevateDB database (and the SQL to create the DB) >>

This is a bizarre one.  I'm still looking into it and will let you know.

--
Tim Young
Elevate Software
www.elevatesoft.com