Hello again;
see attached.
Migrating from DBISAM4 to edb1.08
Question: is there a migration report to tell me where the error in the attached occurrred.
what I am doing is to deleteing the source tables that were successful (migrated)  and run again.  This is a burden.

Allan

Allan


I don't think there's a report, but my bet would be a "forbidden" character in one of the field names.

Roy Lambert

Allan,

<< Migrating from DBISAM4 to edb1.08
Question: is there a migration report to tell me where the error in the
attached occurrred.
what I am doing is to deleteing the source tables that were successful
(migrated)  and run again.  This is a burden. >>

Can you send me the source DBISAM 4 tables ?  They can be empty, I just need
to be able to run them here to see what the issue is.

These types of issues are normal and occur with every upgrade that requires
migration, and we had the same issues with DBISAM upgrades.  There's always
something minor and weird in a table somewhere that isn't taken into
account, and once it's fixed things work just fine.  As Roy said, odd
characters in field names or something similar are usually the culprit.

--
Tim Young
Elevate Software
www.elevatesoft.com