Hi Team,
   This may be one for Tim.
   As you are aware I am migrating a set of Apps and Database from ADS to EDB.
   Several of the tables have an ADS AutoInc field.
   After the migration into EDB all bar one of the autoinc fields has come across correctly as a Generated field.  The
one that doesn't comes across as an Integer only.
   By observation I note that the one that didn't, does not have complete sequential records in the Table.  All the
others do.
   Now, this is not insurmountable as I just use RESTART to reset the record that incrementing starts at once I have set
the field correctly.

   So, the question is - Why doesn't this one table/field come across 'correctly'?

Regards,
Ian

Ian


>    By observation I note that the one that didn't, does not have complete sequential records in the Table. All the
>others do.

Dim memory of my own migrations says this shouldn't be a problem

>    So, the question is - Why doesn't this one table/field come across 'correctly'?

A few thoughts:

- The ADS table is corrupted / its metadata is screwed
- there are nulls in there causing havoc
- Its not defined as an autoinc
- There's some weird set of circumstances that Tim hasn't allowed  for

You're probably right and its down to Tim

Ian,

<< As you are aware I am migrating a set of Apps and Database from ADS to EDB.
Several of the tables have an ADS AutoInc field.
After the migration into EDB all bar one of the autoinc fields has come across correctly as a Generated field.  The
one that doesn't comes across as an Integer only. >>

My guess is that ADS isn't setting the field types properly.  EDB uses the ADS TDataSet components to do its work, so it relies on ADS setting its field types to ftAutoInc, etc. and, if they don't, then EDB has no way of knowing whether the information it is being provided is correct or not.

Tim Young
Elevate Software
www.elevatesoft.com