Skip to main content

You are not logged in. Your edit will be placed in a queue until it is peer reviewed.

We welcome edits that make the post easier to understand and more valuable for readers. Because community members review edits, please try to make the post substantially better than how you found it, for example, by fixing grammar or adding additional resources and hyperlinks.

2
  • I've upvoted you as you pointed me in the right direction. I had not named them to that convention and on changing it, it was pointing SQLEXPRESS. I've fallen for this before and I now have this SO to remind me:). There was a few other issues. I had updated the connection string in the database class library and not in the web app where I was calling it from. The SQLEPRESS issue was the default connectionString in the website which was soon replaced with my own. Thanks @jason-watts Commented May 10, 2016 at 13:54
  • 1
    No problem. Been there myself a few times. Commented May 10, 2016 at 13:59