I had changed some table relationships in my SQLServer database, so in LLBLGenPro I refreshed the catalog then generated the code using Self Servicing Two Class Full/Safe Vs 2005.

When I went back to Visual Studio and did Build I received warnings of duplicate classes in the MyProject.Data.RelationClasses and discovered that a duplicate set of RelationClasses had been created in a RelationClasses subfolder under ValidatorClasses.

I deleted this folder and Generated again and the subfolder was not replaced, but then the project still would not build because it was looking for the deleted classes.

Finally I deleted the whole data folder and re-generated it. As I'm in the early stages of this project this was not a problem.

Has any one else experienced this behaviour?

Before I changed the relationships in SQL, I had been looking in LLBLGenPro to see if it was possible to edit an existing relationship in respect of its cascade-update and cascade delete properties. Perhaps I inadvertently did something to cause this to happen but that seems unlikely.

This is very strange and I personally have not seen it caused due to LLBLGen re-generation of code. However, Plese can you supply details of version number of LLBL you are using the also the RDBMS. Also are you using VS"003 or VS2005, I guess ts 2005 but please cinfirm

Using LLBGenPro 1.0.2005.1, VS2005, SQLServer 2000 Personal Edition version 8.00.194. I'm very busy for the next week. After that I will try to recreate the scenario and see if it happens again. I'll report back when I've done that.

I guess those Relation Classes found under the Validator folder was mistakenly moved to this location. (maybe by a simple mouse drag, it always happens).

Yes, I think you are right.

I did some testing today and could not get this to happen.

Thanks for your time.