As my applications is progressing through development, some of the database desiners are adding/removing indexes, not primary keys but indexes to speed performance. Should this cause any issues with the generated code in adapter scenario and is there any way around it? Index tuning is an ongoing process, I wouldn't want to have to rebuild the LLBLGen code each time an index added.

Thanks In Advance, RC

No indexes don't have any effect on the generated code. So your DBA's should go ahead and add indexes where appropriate. LLBLGen Pro doesn't look at indexes, only constraints.

Together with index tuning, it's often handy to evaluate how filters are constructed in some areas of the application by the developer: it's sometimes more efficient to use a relationcollection + filter instead of a FieldCompareSetPredicate + filter or vice versa (so joins vs. subqueries).