I have installed the fixed UCanAccess 4.0.4 Version, and it works fine for my given Example. BUT in my Application I have "Add Foreign Key" Commands, that have Constraints with non explicit Name. In this Case the Bug is still existant. For a quick fix I changed my Application Code. Now I use only named Constraints. But I think it would be better to fix the UCanAccess that it can process also Constraints that have no Name.
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Hallo,
this Topic is in direct Relation to:
https://stackoverflow.com/questions/49160150/how-can-i-create-a-table-with-two-foreign-key-references-to-one-other-table-via
I have installed the fixed UCanAccess 4.0.4 Version, and it works fine for my given Example. BUT in my Application I have "Add Foreign Key" Commands, that have Constraints with non explicit Name. In this Case the Bug is still existant. For a quick fix I changed my Application Code. Now I use only named Constraints. But I think it would be better to fix the UCanAccess that it can process also Constraints that have no Name.
Thanks for the suggestion. I have created a ticket for the development team.