Oh, yes, unfortunately we have. In fact, we became aware of this for the first time under 2.1.4 and hence thought about the unlikely possibility that it might be some kind of degradation. Since we have not done such validations before, we then validated a long list of backups of this DB (here not .fbk, but frozen compressed .fb), many of which were changed for the last time before the 2.1.4. So we became aware of the fact that the problem must have been there for the long time and going unnoticed.
It seems to be completely irrelevant under which Version this index is being built (as I said, we did not test 1.5) - validations fail but we are not able to notice any other consequences. As I said - backup to .fbk and restore back to .fb have no problems too. We have not seen something like that ever before. Anyway, thank you for your suggestion. Since we do not have any good ideas now, we are eager to hear any possible suggestion. 2011-04-18 14:35:51 Maya Opperman (m...@omniaccounts.co.za): > Have you tried Firebird 2.1.4? Apparently that is > supposed to have sorted this problem out... ------------------------------------------------------------------------------ Benefiting from Server Virtualization: Beyond Initial Workload Consolidation -- Increasing the use of server virtualization is a top priority.Virtualization can reduce costs, simplify management, and improve application availability and disaster protection. Learn more about boosting the value of server virtualization. http://p.sf.net/sfu/vmware-sfdev2dev Firebird-Devel mailing list, web interface at https://lists.sourceforge.net/lists/listinfo/firebird-devel