Copying table from one odb to another odb changes the decimals of numeric fields

When I copy a table from one odb to another odb (Definition and data) all values of the numeric fields are changed.
Example: numeric field (2 decimals) in table to be copied contains 15000.00.
When I copy the table to another odb the value becomes 15000.
2nd example: 5.25 is changed in 0.05.
Looking at the table definitions, they are the same in both odb’s.
Copying the table to calc gives correct results.
Libreoffice version 7.5.5.2 with Firebird

When copying to Calc gives correct result I would also try to copy content from the second *.odb. Might be there is only a formatting problem. You could format the content by clicking on the column header.

15000.00 and 15000 are the same values, but 5.25 and 0.05 seems to be totally wrong. Please add an example to see this behavior here.

I have tried 5 possibilities:

  1. Copy the table to an existing other odb file. Results are wrong.
  2. Copy the complete odb file to a new odb file and then deleted the table in the new odb file. After that I copied the table from the original odb to the new odb (Definition and data). Results are wrong.
  3. Copy the complete odb file to a new odb file and then deleted all records from the table in the new odb file. After that I copied the table from the original odb to the new odb (Append data). Results are wrong.
  4. I have created a completely new database from scratch. Then I copied the table from the original database into it (Definition and data). It was the only thing that I did in the new database but again the result was not correct.
  5. Copy the table from the original odb file to Calc. Results are correct.
  6. I now succeeded the table copy by first making a copy to calc and then copy the calc back to the new table (append data)!

Conclusion: copying tables from odb to odb does not work correctly!

Have tested it now with two database files and reported a bug: Decimal places inserted wrong.
This bug has first reported in 2019, but the reporter didn’t notice he used Firebird. Then he changed the system and Firebird had been set back to experimental. Now bug reporter was glad the bug doesn’t appear (with HSQLDB).
As you see: It was right to set Firebird back to experimental. So we could first find the main bugs and resolve this bugs.
Could you please give a little comment to the bug and set the bug to new?

Thank you RobertG,
I have placed a little comment.