Login ProductsSalesSupportDownloadsAbout |
Home » Technical Support » ElevateDB Technical Support » Support Forums » ElevateDB General » View Thread |
Messages 1 to 3 of 3 total |
Anoither Attempt at Migrating |
Fri, Feb 22 2008 9:41 AM | Permanent Link |
Allan Brocklehurst | 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 Attachments: EDBError.doc |
Fri, Feb 22 2008 11:03 AM | Permanent Link |
Roy Lambert NLH Associates Team Elevate | 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 |
Fri, Feb 22 2008 7:11 PM | Permanent Link |
Tim Young [Elevate Software] Elevate Software, Inc. timyoung@elevatesoft.com | 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 |
This web page was last updated on Tuesday, September 17, 2024 at 04:19 AM | Privacy PolicySite Map © 2024 Elevate Software, Inc. All Rights Reserved Questions or comments ? E-mail us at info@elevatesoft.com |