I've looked at a few threads relating to catalog overwrites on SQL2005 and I was wondering if there is a way to force the generated code to use the catalog specified on the connections string without using the XML config files below.

<sqlServerCatalogNameOverwrites> <add key="OldNameCatalog1" value="" /> </sqlServerCatalogNameOverwrites>

I use my own encrypted config file which contains the connection string and I set the DbUtils.ActualConnectionString at application startup, so it would be handy to always use the catalog set in the connection string.

Thanks, Mark

In SelfServicing that's the only way (putting that lines into your .config), AFAIK. Is there any problem in including this in your .config file?

Using the config file to prevent catalog overwriting is fine for testing but not a good idea for a production application (IMHO). If the config gets deleted the catalog may change without the connection string being changed and if the userid/pw has access to more than one catalog - chaos ensues!

Do you know when the config gets read and by which bit of code - I presumed it was in the ORMSUpport classes or the SqlDQE.

Thanks M

Do you know when the config gets read and by which bit of code - I presumed it was in the ORMSUpport classes or the SqlDQE.

It's read in the static CTor of the SD.LLBLGen.Pro.DQE.SqlServer.DynamicQueryEngine class