Relationnames differ from previous so that all of my .net codes using this code gives an error.

Thank you

rpb1.Relations.Add(FiFoyOdemePlaniEntity.Relations.FiBankaHesapEntityUsingFromBankaKoduFromOrgFirmaFromSubeKoduFromMusteriNoFromBankaHesapNo, "BankaRel2", JoinHint.Left); -- old

rpb1.Relations.Add(FiFoyOdemePlaniEntity.Relations.FiBankaHesapEntityUsingFromBankaHesapNoFromBankaKoduFromMusteriNoFromOrgFirmaFromSubeKodu, "BankaRel2", JoinHint.Left); -- new

This is a breaking change unfortunately, as the naming in old versions (< 3) could lead to duplicates. If you're not migration from a very old version, it might be the order of the pk fields are different. In your previous post I pointed you to the way to make sure the order of the PK fields is in an order you want.

We created a new LLBLGEN 4.2. Project, refresh and add entities (not migrate)

we are sure that tables field orders are true. But foreignkeynames are different. Is there any way to change foreignkeynames as OLD ?

what does 'old' mean in you case?

rpb1.Relations.Add(FiFoyOdemePlaniEntity.Relations.FiBankaHesapEntityUsingFromBankaKoduFromOrgFirmaFromSubeKoduFromMusteriNoFromBankaHesapNo, "BankaRel2", JoinHint.Left); -- old

PAZIMLI wrote:

rpb1.Relations.Add(FiFoyOdemePlaniEntity.Relations.FiBankaHesapEntityUsingFromBankaKoduFromOrgFirmaFromSubeKoduFromMusteriNoFromBankaHesapNo, "BankaRel2", JoinHint.Left); -- old

Heh yeah I got that from your first post But what does 'old' mean, i.e. was it generated with an old version, and if so, which one, etc.

Sorry, Old version 2.5

This looks like the known breaking change stated before. Unfortunately, you will need to modify your code to use the new naming.