Happy New Year!

I hate bringing in the new year with a report of an error, but this is
puzzling me and before a I write a long script to get around it, I want
to make sure it's really an error and not something stupid on my part.

I have two databases and I'm trying to copy records from a table in one
database to the exact same table in a different database with an INSERT
statement like the following:

 INSERT INTO DB1.MyTable
 SELECT * FROM DB2.MyTable
 WHERE DocNum NOT IN (SELECT DocNum FROM DB1.MyTable)

I immediately receive the following error:

 ElevateDB Error #601 The table MyTable is corrupt
 (Error reading rows into cache)

I ran Repair on "MyTable" and it appears to be fine.  I confirmed the
two table strctures are identical (constraints, indexes, collation,
everything).  But then I checked the primary keys (an auto-inc ID
field) and realized the insert would generate records with duplicate
keys.

So I rewrote the INSERT/SELECT to list all the fields except the ID
field and tried again.

Same error message.

I ran the SQL in EDB Manager 2.02 b6 from my Win XP-64 machine against
a remote database on the LAN running 2.02 b6 on Windows 2008 Server.

Any ideas?

--
David Cornelius
CorneliusConcepts.com

David,

<< I immediately receive the following error:

 ElevateDB Error #601 The table MyTable is corrupt (Error reading rows into
cache)

I ran Repair on "MyTable" and it appears to be fine.  I confirmed the two
table strctures are identical (constraints, indexes, collation, everything).
But then I checked the primary keys (an auto-inc ID field) and realized the
insert would generate records with duplicate keys. >>

Per email, you indicate that it appears to be related to the BLOB columns in
the table(s).   I'll be checking into this shortly over the weekend.  I'm
still knee-deep in 2.03 code and need to get the 2.02 B6 code set up before
I can look into this further.

--
Tim Young
Elevate Software
www.elevatesoft.com