Table names/connectionstring conflicts

  •  05-02-2007, 8:37 AM

    Table names/connectionstring conflicts

    I'm wanting to try this environment as a part of a system I've developed. It turns out that it shares data table names with my own application, which means I'll need to create and maintain a separate database for this. That wouldn't be a big whoop, except that the web.config connection string variable I'm using is also identical to CuteChat's...

    <add key="ConnectionString" value="server=(local);database=CutechatStandalone;uid=test;pwd=test"/>

    ...which, I'm assuming, means I'd have to change the variable name in all of my code to accomodate CuteChat.

    Am I right, or is there a workaround for this issue?





View Complete Thread