DBISAM v. 3.30
  ...
                                 XXX.DeleteAllIndexes;
here the error ==>      XXX.AddIndex('GRUPPO','GRUPPO;DESCRIZIONE', []);
                                 XXX.OptimizeTable('GRUPPO',True);
  ...



No Primary Index defined
No required fields defined
Only one secondary index defined as 'GRUPPO;DESCRIZIONE'

During the runtime I get the following error:
>>DBISAM Engine Error # 9729 Duplicate key found in the index 'Sys Deleted'
>>of the table 93320.

Any idea ?

Carlos

Carlos,

<< DBISAM v. 3.30
  ...
                                 XXX.DeleteAllIndexes;
here the error ==>      XXX.AddIndex('GRUPPO','GRUPPO;DESCRIZIONE', []);
                                 XXX.OptimizeTable('GRUPPO',True);
  ...

No Primary Index defined
No required fields defined
Only one secondary index defined as 'GRUPPO;DESCRIZIONE'

During the runtime I get the following error: >>

I can't offer you any fixes for DBISAM 3.x, but I would recommend that you
delete the indexes individually using DeleteIndex instead of using
DeleteAllIndexes, and see if that works better.  If it doesn't, then I would
suggest placing a RepairTable call after you delete the indexes to see if
that can correct the issue.

--
Tim Young
Elevate Software
www.elevatesoft.com

"Tim Young [Elevate Software]" <timyoung@elevatesoft.com> ha scritto nel
messaggio news:78F2D20A-8C84-40DF-B865-96BF351A7523@news.elevatesoft.com...
> Carlos,
>
> << DBISAM v. 3.30
>   ...
>                                  XXX.DeleteAllIndexes;
> here the error ==>      XXX.AddIndex('GRUPPO','GRUPPO;DESCRIZIONE', []);
>                                  XXX.OptimizeTable('GRUPPO',True);
>   ...
>
> No Primary Index defined
> No required fields defined
> Only one secondary index defined as 'GRUPPO;DESCRIZIONE'
>
> During the runtime I get the following error: >>
>
> I can't offer you any fixes for DBISAM 3.x, but I would recommend that you
> delete the indexes individually using DeleteIndex instead of using
> DeleteAllIndexes, and see if that works better.  If it doesn't, then I
> would suggest placing a RepairTable call after you delete the indexes to
> see if that can correct the issue.
>
> --
> Tim Young
> Elevate Software
> www.elevatesoft.com
>


Thank you
I resolved by doubling the DAT with a query
SELECT * FROM XXX
I saved the result, threw the old DAT and renamed the new.
Now everything works fine.

Thanks for support

Carlos