Hi Team,
EDB v 2.28.  Using EDB Manager.

Migrating an ADS DB to EDB.  Of 35 tables to migrate, 24 now appear in EDB.

The migration stopped with the following error..
"ElevateDB Error #202 An error occurred with the module edbmigrateads (Module execution error: Unknown field type (19) encountered.)"

I presume this is due to an issue with a field in the 25th table however the migration tables listing doesn't appear to be in any order that I can tell.

How do I find which table the error occurred please?

Regards & TIA,
Ian

So.  After much sleuthing and gnashing of teeth, multiple repetitions of the Migration process, etc, etc..

It turns out the Migrator doesn't like ADS v 12 LongInts, can't speak for any earlier versions.

Change the LongInt to a normal Integer and all good.  Not good for me/my customer as they have very large integers in their data, hence the LongInt.

Sigh!

Ian


You can either try and patch the migrator yourself or report to Tim - I have a suspicion he may have missed this since ElevateDB now supports BigInt

LARGEINT
This type has been renamed to BIGINT.

I'm not sure when this happened since all I have to go on is the date the web page was updated:

This web page was last updated on
Wednesday, May 9, 2018 at 01:03 PM


Roy Lambert

Roy Lambert wrote:

You can either try and patch the migrator yourself or report to Tim.

Hi Roy,
Not sure what is going to happen with your text above, we'll see.
I have reported it to Tim.
I had a quick look to find the migrator code but couldn't identify it.
Regards,
Ian

Ian


On my system the migrators are all under

C:\3rdParty\EDBUtils\libs


Roy Lambert

<< It turns out the Migrator doesn't like ADS v 12 LongInts, can't speak for any earlier versions.

Change the LongInt to a normal Integer and all good.  Not good for me/my customer as they have very large integers in their data, hence the LongInt. >>

Per email:

"Please send over the ADS table files (and data dictionary, if you're using one) and I will take a look.  It may or may not be something that I can fix, depending upon how ADS maps their data types in the TDataSet layer.  The EDB migration code is already handling 64-bit integers (ftLargeInt), so ADS must be mapping the type to something else.  So, my ability to fix this will be based upon whether I can tell what type the field is using."

However, after reading your description here, I can tell you exactly what the issue is: the EDB migrator is compiled using ADS 11.x, not ADS 12.x.  I can't get access to 12.x in order to use it.

IOW, the error is coming from ADS, not EDB.

Tim Young
Elevate Software
www.elevatesoft.com

>> Tim Young [Elevate Software] wrote:

>> IOW, the error is coming from ADS, not EDB.

Now that's going to be a bummer.