Login ProductsSalesSupportDownloadsAbout |
Home » Technical Support » ElevateDB Technical Support » Support Forums » ElevateDB General » View Thread |
Messages 1 to 4 of 4 total |
Error 406 When Migrating Data |
Thu, Dec 6 2007 5:05 PM | Permanent Link |
Gordon Turner | I'm trying to migrate some DBISAM 2 data into ElevateDB. I copied the
DBISAM 2 Unicode migrator to the configuration file folder (as I'm using the Unicode version of ElevateDB), created a new Database, clicked on the Migrate Data option, entered the path name to the existing data files in the DatabaseDirectory parameter value and when I click on the OK button I get the following error... ElevateDB Error #406 Invalid table identifier 'accrual.dat' Accrual is the name of the first data file in the existing folder so I'm not sure what the problem is, or why I can't migrate the data into the new database. I've tried validating the DBISAM tables, putting quotes around the path name for the DatabaseDirectory, deleting the Accrual data file and get the same result every time. (Deleting the Accrual data file just produces the same message for the next table in the folder.) What am I doing wrong here? -- Gordon Turner Mycroft Computing http://www.mycroftcomputing.com |
Fri, Dec 7 2007 3:29 PM | Permanent Link |
Tim Young [Elevate Software] Elevate Software, Inc. timyoung@elevatesoft.com | Gordon,
<< I'm trying to migrate some DBISAM 2 data into ElevateDB. I copied the DBISAM 2 Unicode migrator to the configuration file folder (as I'm using the Unicode version of ElevateDB), created a new Database, clicked on the Migrate Data option, entered the path name to the existing data files in the DatabaseDirectory parameter value and when I click on the OK button I get the following error... ElevateDB Error #406 Invalid table identifier 'accrual.dat' >> It's a bug. I'll make sure that it's fixed in the next build. -- Tim Young Elevate Software www.elevatesoft.com |
Fri, Dec 7 2007 4:20 PM | Permanent Link |
Gordon Turner | Tim Young [Elevate Software] wrote:
> > It's a bug. I'll make sure that it's fixed in the next build. OK, thanks for letting me know. Is this a problem for all the migrators or only the version 2 migrator. (I can convert the tables to version 4 using the SysUtil program from that version and then migrate if necessary - at least for my development and testing.) -- Gordon Turner Mycroft Computing http://www.mycroftcomputing.com |
Mon, Dec 10 2007 12:17 PM | Permanent Link |
Tim Young [Elevate Software] Elevate Software, Inc. timyoung@elevatesoft.com | Gordon,
<< OK, thanks for letting me know. Is this a problem for all the migrators or only the version 2 migrator. (I can convert the tables to version 4 using the SysUtil program from that version and then migrate if necessary - at least for my development and testing.) >> It's only an issue with the version 2 migrator. It's the way the TDBISAMSession.GetTableNames method works in V2 - it returns file extensions for tables when 3.x and 4.x do not. -- Tim Young Elevate Software www.elevatesoft.com |
This web page was last updated on Tuesday, April 30, 2024 at 03:55 PM | Privacy PolicySite Map © 2024 Elevate Software, Inc. All Rights Reserved Questions or comments ? E-mail us at info@elevatesoft.com |