Ken, What tag you put the connection string in, is irrelevant, because we do not know how you are retrieving the connection string. If your existing code picks it from an appSettings element, then you can use that. If it picks it from a ConnectionStrings element, then use what they have suggested. You're not providing us enough details to be able to troubleshoot the problem.
I think you need someone more experienced with this stuff to take a look at the existing setup. I could take a look if you would contact me on my mail with FTP details of the server. On Sep 16, 11:06 am, OccasionalFlyer <[email protected]> wrote: > My web site broke last week and my ISP claims it is because I need a > connection string in my web.config. Of course, the fact that the site > has function for years without that seems irrelevant to them, but I > digress. I have looked at a _bunch_ of examples from a Google search > of how to do this but none of them has given me the info I need. The > ISP said to add this: > > connectionString="Data Source=VCNSQL82\I82;Initial Catalog=ibr1;User > ID=ibr12;Password=ibr12" providerName="System.Data.SqlClient" > > However, from the examples, I see that this needs to be inside > <appSettings> > > </appSettings> > > Beyond that, however, I see all sorts of different things to do and no > explanation of the exact details, like how to pick a name for a > connection string. Can someone help me out with what I need to insert > into the above connectionString for proper syntax? > > Also, the ISP said that after I do this, I need to compile the > site. I have no idea how to do that. Shouldn't, however, the XML of > web.config be read on the fly, not compiled? Thanks. > > Ken
