The Database Update Framework

In the method "ApiTableCopyData" there is the following line:

Copy_Records hFromTable to hToTable using 0 Callback Self

I suggest to add another parameter here to limit the number of records copied during an initial migration from embedded to SQL.

Copy_Records hFromTable to hToTable iMaxLimit using 0 Callback Self

This is especially useful when developing your migration methods and you are working with a large database. For example, during dev time, I'd like to start off only copying 10 records from each table, just to see that the migration works. This is HUGE time saver.

As I build up the migration, I would increase this number.

For production, this variable (iMaxLimit) would always be set to ZERO, meaning to copy all records.