The project is pretty large, it would take me some time to strip it down to a workable repro project.
If I have to I will do so but here's some of the other info you asked about. Here is an example error message:
The relationship 'SafariNow.SellerProduct.Accommodation - SafariNow.Accommodation.SellerProduct (1:1)' has been removed because its underlying foreign key constraint wasn't found in the refreshed relational model data.
ANd here is the relevant DDL for the foreign key constraint:
USE [SafariNow]
GO
ALTER TABLE [dbo].[Accommodation]
WITH NOCHECK ADD CONSTRAINT [FK_tblAccommodationBb_tblSellerProduct] FOREIGN KEY([Operator_ID])
REFERENCES [dbo].[SellerProduct] ([SPID])
ON UPDATE CASCADE
ON DELETE CASCADE
GO
ALTER TABLE [dbo].[Accommodation] CHECK CONSTRAINT [FK_tblAccommodationBb_tblSellerProduct]
GO
Because LLBLGen feels the model is out of synch it strongly suggests I synch. I ran the following suggested DDL from the SQL generator
USE [SafariNow]
GO
ALTER TABLE [dbo].[Accommodation] WITH CHECK ADD CONSTRAINT [FK_16aaa434164939c2e7fa910190a] FOREIGN KEY([Operator_ID])
REFERENCES [dbo].[SellerProduct] ([SPID])
GO
ALTER TABLE [dbo].[Accommodation] CHECK CONSTRAINT [FK_16aaa434164939c2e7fa910190a]
GO
So now there are in fact two constraints doing the same thing, but the generator want to drop this relation.
I am running LLBLGEN 3.0 Final
These are the binaries I have:
SD.LLBLGen.Pro.ApplicationCore, Version=3.0.0.0, Culture=neutral, PublicKeyToken=ca73b74ba4e3ff27
SD.LLBLGen.Pro.Core, Version=3.0.0.0, Culture=neutral, PublicKeyToken=ca73b74ba4e3ff27
SD.LLBLGen.Pro.DBDriverCore, Version=3.0.0.0, Culture=neutral, PublicKeyToken=ca73b74ba4e3ff27
SD.LLBLGen.Pro.GeneratorCore, Version=3.0.0.0, Culture=neutral, PublicKeyToken=ca73b74ba4e3ff27
SD.LLBLGen.Pro.DBDrivers.SqlServerDBDriver, Version=3.0.0.0, Culture=neutral, PublicKeyToken=ca73b74ba4e3ff27
Not sure what else you need?
