Hi,

I am migrating the embedded Dataflex for the first time through the SQL conversion Wizard (DF20-RC1).


Everything worked like magic, . . .
Except for 1 database. . .
Always have one .

Code:
------------------------------------------------------------
Converting Recnum table: 14, BORDERO, @Bordero - V.19.02
Progress:Start time: 09/03/2021 17:11:01,175
Start time: 09/03/2021 17:11:01,175
Structure_Start
Structure_Copy
Set_Attribute DF_INDEX_SQL_PRIMARY_KEY to 1
AssignMinimalLength
RealignOverlaps
Structure_End
Progress:Starting restructure transaction.
Starting restructure transaction.
Progress:Creating new table.
Creating new table.
Progress:Creating primary key BORDERO001_PK.
Creating primary key BORDERO001_PK.
Progress:Creating index BORDERO002.
Creating index BORDERO002.
Progress:Creating index BORDERO003.
Creating index BORDERO003.
Progress:Creating index BORDERO004.
Creating index BORDERO004.
Progress:Creating index BORDERO005.
Creating index BORDERO005.
Progress:Creating index BORDERO006.
Creating index BORDERO006.
Progress:Creating index BORDERO007.
Creating index BORDERO007.
Progress:Creating index BORDERO008.
Creating index BORDERO008.
Progress:Creating index BORDERO009.
Creating index BORDERO009.
Progress:Creating index BORDERO010.
Creating index BORDERO010.
Progress:Creating index BORDERO000.
Creating index BORDERO000.
Progress:Creating intermediate file.
Creating intermediate file.
Progress:Commit restructure transaction.
Commit restructure transaction.
CLI_DROPINDICES
Progress:Temporary delete of all indices of table BORDERO.
Temporary delete of all indices of table BORDERO.
Progress:Dropping primary key BORDERO001_PK.
Dropping primary key BORDERO001_PK.
Progress:Dropping index BORDERO000.
Dropping index BORDERO000.
Progress:Dropping index BORDERO002.
Dropping index BORDERO002.
Progress:Dropping index BORDERO003.
Dropping index BORDERO003.
Progress:Dropping index BORDERO004.
Dropping index BORDERO004.
Progress:Dropping index BORDERO005.
Dropping index BORDERO005.
Progress:Dropping index BORDERO006.
Dropping index BORDERO006.
Progress:Dropping index BORDERO007.
Dropping index BORDERO007.
Progress:Dropping index BORDERO008.
Dropping index BORDERO008.
Progress:Dropping index BORDERO009.
Dropping index BORDERO009.
Progress:Dropping index BORDERO010.
Dropping index BORDERO010.
CLI_BCP
Progress:Copy records in groups of 1000
Progress:All records copied.
All records copied.
CLI_CREATEINDICES
Progress:Re-creating temporary deleted indices of table BORDERO.
Re-creating temporary deleted indices of table BORDERO.
Progress:Creating primary key BORDERO001_PK.
Creating primary key BORDERO001_PK.
Progress:ERROR 12289: Erro genérico. 23000 (1505)--[Microsoft][ODBC Driver 17 for SQL Server][SQL Server]A instrução CREATE UNIQUE INDEX foi encerrada porque foi encontrada uma chave duplicada para o nome de objeto 'dbo.BORDERO' e o nome de índice 'BORDERO001_PK'. O valor da chave duplicada é (gl, 1064, 2019-03-26, 54, 5).  Table = BORDERO (251), Source = MSSQLDRV.Structure_End.CreateIndexes
ERROR 12289: Erro genérico. 23000 (1505)--[Microsoft][ODBC Driver 17 for SQL Server][SQL Server]A instrução CREATE UNIQUE INDEX foi encerrada porque foi encontrada uma chave duplicada para o nome de objeto 'dbo.BORDERO' e o nome de índice 'BORDERO001_PK'. O valor da chave duplicada é (gl, 1064, 2019-03-26, 54, 5).  Table = BORDERO (251), Source = MSSQLDRV.Structure_End.CreateIndexes
Progress:Failed to create primary key BORDERO001_PK of table BORDERO.
Failed to create primary key BORDERO001_PK of table BORDERO.
Progress:Creating index BORDERO000.
Creating index BORDERO000.
Progress:Creating index BORDERO002.
Creating index BORDERO002.
Progress:Failed to create index BORDERO002 of table BORDERO.
Failed to create index BORDERO002 of table BORDERO.
Progress:Creating index BORDERO003.
Creating index BORDERO003.
Progress:Failed to create index BORDERO003 of table BORDERO.
Failed to create index BORDERO003 of table BORDERO.
Progress:Creating index BORDERO004.
Creating index BORDERO004.
Progress:Failed to create index BORDERO004 of table BORDERO.
Failed to create index BORDERO004 of table BORDERO.
Progress:Creating index BORDERO005.
Creating index BORDERO005.
Progress:Failed to create index BORDERO005 of table BORDERO.
Failed to create index BORDERO005 of table BORDERO.
Progress:Creating index BORDERO006.
Creating index BORDERO006.
Progress:Failed to create index BORDERO006 of table BORDERO.
Failed to create index BORDERO006 of table BORDERO.
Progress:Creating index BORDERO007.
Creating index BORDERO007.
Progress:Failed to create index BORDERO007 of table BORDERO.
Failed to create index BORDERO007 of table BORDERO.
Progress:Creating index BORDERO008.
Creating index BORDERO008.
Progress:Failed to create index BORDERO008 of table BORDERO.
Failed to create index BORDERO008 of table BORDERO.
Progress:Creating index BORDERO009.
Creating index BORDERO009.
Progress:Failed to create index BORDERO009 of table BORDERO.
Failed to create index BORDERO009 of table BORDERO.
Progress:Creating index BORDERO010.
Creating index BORDERO010.
Progress:Failed to create index BORDERO010 of table BORDERO.
Failed to create index BORDERO010 of table BORDERO.
Progress:Failed to recreate 10 indices.
Failed to recreate 10 indices.
Close hSQLTable
Close ahTables[iCount]
Progress:ERROR 4118: Impossível excluir arquivo
ERROR 4118: Impossível excluir arquivo
Progress:End time: 09/03/2021 17:11:06,071
End time: 09/03/2021 17:11:06,071
Progress:Total time to convert table: 0:0:0:4,896
Total time to convert table: 0:0:0:4,896

Analyzing I saw that it was duplicate records, which in the embedded, did not accuse me after all, I have the parameter: Ignore Case unchecked.
Click image for larger version. 

Name:	bugsql1.JPG 
Views:	15 
Size:	162.5 KB 
ID:	14374


I searched the help and got the answer, that SQL does not consider this and in a way, as only 4 records were the cause, I don't mind making an addition to the duplicate descriptors.


So I ask:
1) Although the error occurred I noticed that the SQL database was generated, but without the indexes, and as stated in the message, this was not excluded due to some type of impediment: Should it or not?


2) At first I thought that it was just my index 1, in which I changed the record and in this case the error occurred only in relation to the information in index 10, but not with the information of which record, which could seem to be a problem in another thing. I took a deep breath and having already experienced question 1, it was the same case of duplicity, so because in this case the message record was not displayed.
Code:
------------------------------------------------------------
Converting Recnum table: 14, BORDERO, @Bordero - V.19.02
Progress:Start time: 10/03/2021 07:24:19,787
Start time: 10/03/2021 07:24:19,787
Structure_Start
Structure_Copy
Set_Attribute DF_INDEX_SQL_PRIMARY_KEY to 1
AssignMinimalLength
RealignOverlaps
Structure_End
Progress:Starting restructure transaction.
Starting restructure transaction.
Progress:Creating new table.
Creating new table.
Progress:Creating primary key BORDERO001_PK.
Creating primary key BORDERO001_PK.
Progress:Creating index BORDERO002.
Creating index BORDERO002.
Progress:Creating index BORDERO003.
Creating index BORDERO003.
Progress:Creating index BORDERO004.
Creating index BORDERO004.
Progress:Creating index BORDERO005.
Creating index BORDERO005.
Progress:Creating index BORDERO006.
Creating index BORDERO006.
Progress:Creating index BORDERO007.
Creating index BORDERO007.
Progress:Creating index BORDERO008.
Creating index BORDERO008.
Progress:Creating index BORDERO009.
Creating index BORDERO009.
Progress:Creating index BORDERO010.
Creating index BORDERO010.
Progress:Creating index BORDERO000.
Creating index BORDERO000.
Progress:Creating intermediate file.
Creating intermediate file.
Progress:Commit restructure transaction.
Commit restructure transaction.
CLI_DROPINDICES
Progress:Temporary delete of all indices of table BORDERO.
Temporary delete of all indices of table BORDERO.
Progress:Dropping primary key BORDERO001_PK.
Dropping primary key BORDERO001_PK.
Progress:Dropping index BORDERO000.
Dropping index BORDERO000.
Progress:Dropping index BORDERO002.
Dropping index BORDERO002.
Progress:Dropping index BORDERO003.
Dropping index BORDERO003.
Progress:Dropping index BORDERO004.
Dropping index BORDERO004.
Progress:Dropping index BORDERO005.
Dropping index BORDERO005.
Progress:Dropping index BORDERO006.
Dropping index BORDERO006.
Progress:Dropping index BORDERO007.
Dropping index BORDERO007.
Progress:Dropping index BORDERO008.
Dropping index BORDERO008.
Progress:Dropping index BORDERO009.
Dropping index BORDERO009.
Progress:Dropping index BORDERO010.
Dropping index BORDERO010.
CLI_BCP
Progress:Copy records in groups of 1000
Progress:All records copied.
All records copied.
CLI_CREATEINDICES
Progress:Re-creating temporary deleted indices of table BORDERO.
Re-creating temporary deleted indices of table BORDERO.
Progress:Creating primary key BORDERO001_PK.
Creating primary key BORDERO001_PK.
Progress:Creating index BORDERO000.
Creating index BORDERO000.
Progress:Creating index BORDERO002.
Creating index BORDERO002.
Progress:Creating index BORDERO003.
Creating index BORDERO003.
Progress:Creating index BORDERO004.
Creating index BORDERO004.
Progress:Creating index BORDERO005.
Creating index BORDERO005.
Progress:Creating index BORDERO006.
Creating index BORDERO006.
Progress:Creating index BORDERO007.
Creating index BORDERO007.
Progress:Creating index BORDERO008.
Creating index BORDERO008.
Progress:Creating index BORDERO009.
Creating index BORDERO009.
Progress:Creating index BORDERO010.
Creating index BORDERO010.
Progress:Failed to create index BORDERO010 of table BORDERO.
Failed to create index BORDERO010 of table BORDERO.
Progress:Failed to recreate 1 indices.
Failed to recreate 1 indices.
Close hSQLTable
Close ahTables[iCount]
Progress:ERROR 4118: Impossível excluir arquivo
ERROR 4118: Impossível excluir arquivo
Progress:End time: 10/03/2021 07:24:23,747
End time: 10/03/2021 07:24:23,747
Progress:Total time to convert table: 0:0:0:3,96
Total time to convert table: 0:0:0:3,96


3) Once the base has been converted and the SQL does not natively support the Ignore Case I would expect that in DbBuilder I would not have this column, as the image display does not match reality and this can cause confusion. Do you agree?
Click image for larger version. 

Name:	bugsql2.JPG 
Views:	14 
Size:	158.4 KB 
ID:	14375

Regards,