Catalog Name Overwriting

Posts   
 
    
jader201
User
Posts: 33
Joined: 20-Mar-2007
# Posted on: 09-May-2007 18:17:26   

We have set up an LLBLGen Pro project using Self-Servicing on a SQL 2005 database. We created the project under the catalog name "LLBLGenPro1".

Now, we need to be able to connect to a different catalog, "LLBLGenPro2". We can get this to work using catalog name overwriting in our app.config file, but only if the original catalog (LLBLGenPro1) is online. Once we take it offline, then we are no longer able to connect to LLBLGenPro2.

Why is this? Is it possible to connect to a different catalog other than what is configured when the project is created? If not, what suggestions do you have for working around this scenario (other than renaming our catalogs, which isn't an option)?

Thanks in advance.

Walaa avatar
Walaa
Support Team
Posts: 14995
Joined: 21-Aug-2005
# Posted on: 09-May-2007 18:26:37   

Did you try to change the catalog name written into the connectionString?

then we are no longer able to connect to LLBLGenPro2

What happens? do you get an error or an exception? (please post it)

Which runtime library version are you using?

jader201
User
Posts: 33
Joined: 20-Mar-2007
# Posted on: 09-May-2007 18:51:24   

Thanks for the quick follow up, Walaa.

I think you lead us to our problem. For some reason, we left our connection string the same, pointing to the original catalog, thinking that the overwrite would override the catalog in the connection string with our overwrite.

After changing the catalog in the connection string, we are now able to connect just fine.

Thanks again for your help.