Thank you for the explanations.
I will change the format and my habits.
Just to explain for understanding (the problems are all solved now, at least I hope so).
I wok in different layers:
1) (kind of, you do not want to know details) US-database = input
2) FP reads it
3) FP works with it and fights those zeros for the first fights
4) FP sends new data to IBX
5) IBX sends the data to Firebird
x) Flamrobin is the helping hand between 4 and 5
What my target is: Firebird must not accept any default value as input for a not existing date, which may come originally from the US-database or my own errors.
And yes, the time needed is ok. The data for this operation are back to 1983. Until the stuff is converted (and filtered and sorted....), it takes this time. I will have a coffee and not do it again after it is converted (I hope so).
In German we say, "the hope is it, what dies at last".
What I hope(d): As Flamerobin checks the date and give correct results in "where" for e.g.
where datum > '10.11.2022'
Is there a chance, that it passes on to Firebird as well "meant" conditions? And "corrects" the format internally?
I am aware, that this where clauses accepts different strange inputs as well, I tried some (but got wrong results).
[Window Title]
About FlameRobin
[Content]
FlameRobin 0.9.3 (git hash 375bec5f) Unicode (x64)
Database administration tool for Firebird RDBMS
This tool uses IBPP library version 2.5.2.1
wxWidgets library version 3.1.4
Copyright (c) 2004-2020 FlameRobin Development Team
http://www.flamerobin.org[OK]