Re: custom ASP programming has clashed with Frontpage DRW pages with SQL INSERT and UPDATE
From: Tim Thorp (Timothy_Thorp_at_brown.edu)
Date: 02/18/04
- Next message: John F. Searight: "Submitting information to Access"
- Previous message: Barb: "cannot add navigation bar"
- In reply to: Kevin Spencer: "Re: custom ASP programming has clashed with Frontpage DRW pages with SQL INSERT and UPDATE"
- Next in thread: Kevin Spencer: "Re: custom ASP programming has clashed with Frontpage DRW pages with SQL INSERT and UPDATE"
- Reply: Kevin Spencer: "Re: custom ASP programming has clashed with Frontpage DRW pages with SQL INSERT and UPDATE"
- Messages sorted by: [ date ] [ thread ]
Date: Wed, 18 Feb 2004 11:31:30 -0500
I will certainly not be referencing any dlls on my web pages going forward,
but I still need to resolve behavior changes to my current pages from when I
did call it in the past.
Is it possible that the server is "remembering" that I called the dll and
still using it in my current pages?
Thanks,
Tim
"Kevin Spencer" <kevin@takempis.com> wrote in message
news:ehS7Ffi9DHA.340@tk2msftngp13.phx.gbl...
> Both Jim and I told you that you shouldn' be referencing any DLL in your
> database connection code. You should use a Connection String to connect to
> your database. You might want to take a look at some of the articles and
> interactive tutorials on my web site to see how it should be used:
> http://www.takempis.com. Here's an example of a Database Connection using
> ADO:
>
> <%
> Set cn = Server.CreateObject("ADODB.Connection")
> cn.Open Application("ConnectionString")
> q = "SELECT * FROM mytable WHERE myfield LIKE 'my goodness!'"
> Set rs = cn.Execute(q)
>
> ' Do something with the result set
>
> rs.Close
> Set rs = Nothing
> cn.Close
> Set cn = Nothing
> %>
>
> It is certainly fine to have both FrontPage DRW pages and your own cuatom
> ASP pages on the same site. The FrontPage DRW pages uses an
> automatically-generated Connection String in the global.asa file. You can
> also store your Connection String there, or, better yet, use the one that
> FrontPage generated, if you're connecting to the same Data Source.
>
> --
> HTH,
> Kevin Spencer
> .Net Developer
> Microsoft MVP
> Big things are made up
> of lots of little things.
>
> "Tim Thorp" <Timothy_Thorp@brown.edu> wrote in message
> news:OoRFuWi9DHA.452@TK2MSFTNGP11.phx.gbl...
> > Thanks Jon, Kevin & Jim! I have a few response questions:
> >
> > Jon, is it OK to have custom asp pages and frontpage DRW pages in the
same
> > site? or do I need to make another site?
> >
> > Jim, you seem to know about the msado15.dll file. Is it possible that
when
> I
> > called it on a specific page (not in the global.asa) that other pages in
> the
> > site are being confused by this msado15.dll? If so, can I turn off
> > msado15.dll? I must really sound like a newbie on this one, so pardon my
> > weird question. I was merely following the instructions on page 573 of
> WROX
> > Beginning ASP 3.0 and have had errors on my site since then.
> >
> > Thanks for all the help!!! Soon I will be custom coding my own asp
pages.
> >
> > Tim
> >
> > "Tim Thorp" <Timothy_Thorp@brown.edu> wrote in message
> > news:%23H6qeRZ9DHA.2480@TK2MSFTNGP10.phx.gbl...
> > > In a nutshell, things that used to work on my site have stopped
working
> > and
> > > the error seems to have occurred since I called the msado15.dll file
in
> a
> > > custom ASP file.
> > > A LITTLE MORE BACKGROUND INFO:
> > > I created an ASP site in MS Frontpage 2003 with an Access database to
> > store
> > > and report on my departments training events, registrations and
> > evaluations.
> > > The site worked pretty well, but I wanted to take some functionality
to
> a
> > > higher level and found that I had exausted the capabilities of the
> > Frontpage
> > > Database Results Wizard, so I stared to read about creating ASP pages
in
> > > Beginning ASP 3.0 (WROX press).
> > > WHEN THE PROBLEM AROSE:
> > > I only have permission to make web sites at one web server, so I
thought
> I
> > > would integrate some custom ASP pages with my exiting database and
> > Frontpage
> > > generated ASP pages. In my experimenting, I used datastore.asp to
> connect
> > to
> > > the database and also called the metadata type="typelib"
> File="C:\Program
> > > Files\...\msado15.dll". In the process of experimenting with the code,
I
> > > made some great progress in learning to use ASP and hope to continue
> > > learning again soon.
> > > WHAT IS THE PROBLEM:
> > > After I was done with my custom ASP work, I needed to do some work on
> some
> > > other pages in my site and started to receive error messages on pages
> that
> > > used to work fine. Specifically on pages which have database results
> with
> > > Custom SQL statements containing UPDATE or INSERT queries. Here are
two
> > > error messages: "Database Results Wizard Error
> > > Unable to find operator in query string. Query string currently is
> INSERT
> > > INTO registrations (fname, lname, email, phone, dept, platform,
attend,
> > > eventID, precourse_status) VALUES ('::fname::', '::lname::',
> '::email::',
> > > '::phone::', '::dept::', '::platform::', '::attend::', ::eventID::,
> > > '::precourse_status::')" and "Database Results Wizard Error
> > > Your page contains a query with user input parameters that could not
be
> > > resolved.
> > > This could happen if your DatabaseRegionStart webbot has an empty or
> > missing
> > > s-columnnames or s-columntypes attributes."
> > >
> > >
> > >
> >
> >
>
>
- Next message: John F. Searight: "Submitting information to Access"
- Previous message: Barb: "cannot add navigation bar"
- In reply to: Kevin Spencer: "Re: custom ASP programming has clashed with Frontpage DRW pages with SQL INSERT and UPDATE"
- Next in thread: Kevin Spencer: "Re: custom ASP programming has clashed with Frontpage DRW pages with SQL INSERT and UPDATE"
- Reply: Kevin Spencer: "Re: custom ASP programming has clashed with Frontpage DRW pages with SQL INSERT and UPDATE"
- Messages sorted by: [ date ] [ thread ]
Relevant Pages
|