Thanks for the offer.  I used my ftp tool to find all the config files
on my site and looked at the web.config and app.config files. One
web.config file that I think is no longer used did have incorrect
values in it and I changed it.  The main web.config file for the site,
however, had no connectionString code at all.  I didn't think it would
help but I added an entry in that file anyway.  When this did not
help, the ISP told me to change a custom dll to fix the
connectionString.  I've asked them to show me evidence that this is
the problem because it looks to me like they are just guessing.  I've
not had any experience writing or creating dlls, so I want them to
justify their request before I spend twelve or fourteen hours trying
to learn to create dlls and then figure out where the code for it
is.   So thanks for the offer, but unless you are ready to delve into
something harrier, I don't want to impose.  A dll is a bigger problem
than a config file.

Ken

On Sep 20, 8:51 pm, May0rDav3 <[email protected]> wrote:
> If you have access to the web.config and app.config files, I would be
> happy to take a look at them to at least try to determine how it is
> (or rather was) connecting to the database.  Please feel free to
> change any identifying values prior to emailing if you wish.
>
> On Sep 19, 10:13 pm, OccasionalFlyer <[email protected]> wrote:
>
> > Well, however this might sound, I was asked to take over
> > administration of the site so that he previous administrator would
> > have time for a large research project/book.  I was told I'd be adding
> > HTML, tweaking web pages and such.  My web programming knowledge is in
> > technologies other than ASP.NET.  I've done reading in a couple of
> > ASP.NET programming books but I didn't get what I need to do here I
> > guess.  I've looked through web.config., app.config, and the site's
> > BIN directory and found nothing.  All I know is that the ISP says we
> > are still using the legacy MSSQL server and need a new connection
> > string.  I don't know where to find that.  So I cannot tell you how
> > the site currently accesses the database. Thanks.
>
> > Ken
>
> > On Sep 16, 1:08 am, Cerebrus <[email protected]> wrote:
>
> > > 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

Reply via email to