I would be greatly indebted to anyone who has an idea as to where I should
be looking for a solution to this problem. I've developed a number of
custom queries using the FP2002's DBRW and an Access 2002 database, and they
have worked flawlessly for the last two years. About a month ago, about 2/3
of these queries started returning errors like "Your page contains a query
with user input parameters that could not be resolved." and
"ADODB.Recordset error '800a0cc1' ". At first I thought it was my hosting
service's servers that were to blame (after all, I hadn't changed anything
to cause the problem), but I just changed providers and the problems
persist. I've done the "compact and repair" on the .mdb file, but the same
errors get returned. I'm at my wit's end on this one. I've looked at the
queries that still work and can find no common denominator between them that
would explain why some work and some don't. Help!

A.D.

See the second part of this KB article:
http://support.microsoft.com/default...b;en-us;817029

--
~ Kathleen Anderson
Microsoft MVP - FrontPage
Spider Web Woman Designs
http://www.spiderwebwoman.com/resources/


Augie Dawg wrote:
> I would be greatly indebted to anyone who has an idea as to where I
> should be looking for a solution to this problem. I've developed a
> number of custom queries using the FP2002's DBRW and an Access 2002
> database, and they have worked flawlessly for the last two years.
> About a month ago, about 2/3 of these queries started returning
> errors like "Your page contains a query with user input parameters
> that could not be resolved." and "ADODB.Recordset error '800a0cc1'
> ". At first I thought it was my hosting service's servers that were
> to blame (after all, I hadn't changed anything to cause the problem),
> but I just changed providers and the problems persist. I've done the
> "compact and repair" on the .mdb file, but the same errors get
> returned. I'm at my wit's end on this one. I've looked at the
> queries that still work and can find no common denominator between
> them that would explain why some work and some don't. Help!
>
> A.D.

I saw that article, but it says it applies to FP 2003. I'm using FP2002.
Also, I looked at the HTML generated, and all s-columnnames and
s-columntypes look just fine. Any other ideas?



"Kathleen Anderson [MVP - FP]" <(E-Mail Removed)> wrote in message
news:(E-Mail Removed)...
> See the second part of this KB article:
> http://support.microsoft.com/default...b;en-us;817029
>
> --
> ~ Kathleen Anderson
> Microsoft MVP - FrontPage
> Spider Web Woman Designs
> http://www.spiderwebwoman.com/resources/
>
>
> Augie Dawg wrote:
>> I would be greatly indebted to anyone who has an idea as to where I
>> should be looking for a solution to this problem. I've developed a
>> number of custom queries using the FP2002's DBRW and an Access 2002
>> database, and they have worked flawlessly for the last two years.
>> About a month ago, about 2/3 of these queries started returning
>> errors like "Your page contains a query with user input parameters
>> that could not be resolved." and "ADODB.Recordset error '800a0cc1'
>> ". At first I thought it was my hosting service's servers that were
>> to blame (after all, I hadn't changed anything to cause the problem),
>> but I just changed providers and the problems persist. I've done the
>> "compact and repair" on the .mdb file, but the same errors get
>> returned. I'm at my wit's end on this one. I've looked at the
>> queries that still work and can find no common denominator between
>> them that would explain why some work and some don't. Help!
>>
>> A.D.
>
>

>> Any other ideas?

Quit using the Data Base Retard Wizard (DBRW) and write your own code.

Bob Lehmann

"Augie Dawg" <(E-Mail Removed)> wrote in message
news:XXdjd.19742$(E-Mail Removed)...
> I saw that article, but it says it applies to FP 2003. I'm using FP2002.
> Also, I looked at the HTML generated, and all s-columnnames and
> s-columntypes look just fine. Any other ideas?
>
>
>
> "Kathleen Anderson [MVP - FP]" <(E-Mail Removed)> wrote in message
> news:(E-Mail Removed)...
> > See the second part of this KB article:
> > http://support.microsoft.com/default...b;en-us;817029
> >
> > --
> > ~ Kathleen Anderson
> > Microsoft MVP - FrontPage
> > Spider Web Woman Designs
> > http://www.spiderwebwoman.com/resources/
> >
> >
> > Augie Dawg wrote:
> >> I would be greatly indebted to anyone who has an idea as to where I
> >> should be looking for a solution to this problem. I've developed a
> >> number of custom queries using the FP2002's DBRW and an Access 2002
> >> database, and they have worked flawlessly for the last two years.
> >> About a month ago, about 2/3 of these queries started returning
> >> errors like "Your page contains a query with user input parameters
> >> that could not be resolved." and "ADODB.Recordset error '800a0cc1'
> >> ". At first I thought it was my hosting service's servers that were
> >> to blame (after all, I hadn't changed anything to cause the problem),
> >> but I just changed providers and the problems persist. I've done the
> >> "compact and repair" on the .mdb file, but the same errors get
> >> returned. I'm at my wit's end on this one. I've looked at the
> >> queries that still work and can find no common denominator between
> >> them that would explain why some work and some don't. Help!
> >>
> >> A.D.
> >
> >
>
>

So if you upgrade to fp2003, you are requiring your isp to have asp.net
to get around snags like that?

>See the second part of this KB article:
>http://support.microsoft.com/default...b;en-us;817029
>
>
>

No, just learn how to hand code your ASP and not rely on the FP database components.

--
==============================================
Thomas A. Rowe (Microsoft MVP - FrontPage)
WEBMASTER Resources(tm)
http://www.ycoln-resources.com
FrontPage Resources, WebCircle, MS KB Quick Links, etc.
==============================================
To assist you in getting the best answers for FrontPage support see:
http://www.net-sites.com/sitebuilder/newsgroups.asp

"Clark" <non-(E-Mail Removed)> wrote in message
news:lKpjd.44552$(E-Mail Removed)...
> So if you upgrade to fp2003, you are requiring your isp to have asp.net to get around snags like
> that?
>
>>See the second part of this KB article:
>>http://support.microsoft.com/default...b;en-us;817029
>>
>>
>

I'm a little surprised at the responses that urges hand coding vs. use of
higher level tools like the FP database components. While they aren't
perfect, I've found them to be great productivity enhancers. I've spent a
fraction of the time developing the database side of my site than if I had
hand coded it. What is the rationale for promoting hand coding? It seems
that if hand coding is better than using the higher level tool, then by
extension we should all be coding in assembly language rather than the
higher level tools like VB Script.

A.D.




"Thomas A. Rowe" <(E-Mail Removed)> wrote in message
news:%23Phf$(E-Mail Removed)...
> No, just learn how to hand code your ASP and not rely on the FP database
> components.
>
> --
> ==============================================
> Thomas A. Rowe (Microsoft MVP - FrontPage)
> WEBMASTER Resources(tm)
> http://www.ycoln-resources.com
> FrontPage Resources, WebCircle, MS KB Quick Links, etc.
> ==============================================
> To assist you in getting the best answers for FrontPage support see:
> http://www.net-sites.com/sitebuilder/newsgroups.asp
>
> "Clark" <non-(E-Mail Removed)> wrote in message
> news:lKpjd.44552$(E-Mail Removed)...
>> So if you upgrade to fp2003, you are requiring your isp to have asp.net
>> to get around snags like that?
>>
>>>See the second part of this KB article:
>>>http://support.microsoft.com/default...b;en-us;817029
>>>
>>>
>>
>
>

>> I've found them to be great productivity enhancers.
How much productivity have you gained in the last day trying to find your
work-around?

>> What is the rationale for promoting hand coding?
Flexibile, more efficient, readable, maintainable code for starters.

>> by extension we should all be coding in assembly language
Extremely bad analogy. The use of high level tools isn't the problem. But,
the automagical DB thing in FP is so bad it is effectively useless for
anything of substance. And, as you are finding out, it is nearly impossible
to work around the constraints it imposes.

Bob Lehmann

"Augie Dawg" <(E-Mail Removed)> wrote in message
news:Hgujd.20388$(E-Mail Removed)...
> I'm a little surprised at the responses that urges hand coding vs. use of
> higher level tools like the FP database components. While they aren't
> perfect, I've found them to be great productivity enhancers. I've spent a
> fraction of the time developing the database side of my site than if I had
> hand coded it. What is the rationale for promoting hand coding? It seems
> that if hand coding is better than using the higher level tool, then by
> extension we should all be coding in assembly language rather than the
> higher level tools like VB Script.
>
> A.D.
>
>
>
>
> "Thomas A. Rowe" <(E-Mail Removed)> wrote in message
> news:%23Phf$(E-Mail Removed)...
> > No, just learn how to hand code your ASP and not rely on the FP database
> > components.
> >
> > --
> > ==============================================
> > Thomas A. Rowe (Microsoft MVP - FrontPage)
> > WEBMASTER Resources(tm)
> > http://www.ycoln-resources.com
> > FrontPage Resources, WebCircle, MS KB Quick Links, etc.
> > ==============================================
> > To assist you in getting the best answers for FrontPage support see:
> > http://www.net-sites.com/sitebuilder/newsgroups.asp
> >
> > "Clark" <non-(E-Mail Removed)> wrote in message
> > news:lKpjd.44552$(E-Mail Removed)...
> >> So if you upgrade to fp2003, you are requiring your isp to have asp.net
> >> to get around snags like that?
> >>
> >>>See the second part of this KB article:
> >>>http://support.microsoft.com/default...b;en-us;817029
> >>>
> >>>
> >>
> >
> >
>
>

When you learn to hand code, you learn ASP/VBScript.

By learn ASP/VBScript you gain the ability to incorporate other functionality that you might need
down the road, which is just not possible to implement when using the FP database components.

For very basic adding or displaying of data the FP database component are a good starting ground.

--
==============================================
Thomas A. Rowe (Microsoft MVP - FrontPage)
WEBMASTER Resources(tm)
http://www.ycoln-resources.com
FrontPage Resources, WebCircle, MS KB Quick Links, etc.
==============================================
To assist you in getting the best answers for FrontPage support see:
http://www.net-sites.com/sitebuilder/newsgroups.asp

"Augie Dawg" <(E-Mail Removed)> wrote in message
news:Hgujd.20388$(E-Mail Removed)...
> I'm a little surprised at the responses that urges hand coding vs. use of higher level tools like
> the FP database components. While they aren't perfect, I've found them to be great productivity
> enhancers. I've spent a fraction of the time developing the database side of my site than if I
> had hand coded it. What is the rationale for promoting hand coding? It seems that if hand coding
> is better than using the higher level tool, then by extension we should all be coding in assembly
> language rather than the higher level tools like VB Script.
>
> A.D.
>
>
>
>
> "Thomas A. Rowe" <(E-Mail Removed)> wrote in message
> news:%23Phf$(E-Mail Removed)...
>> No, just learn how to hand code your ASP and not rely on the FP database components.
>>
>> --
>> ==============================================
>> Thomas A. Rowe (Microsoft MVP - FrontPage)
>> WEBMASTER Resources(tm)
>> http://www.ycoln-resources.com
>> FrontPage Resources, WebCircle, MS KB Quick Links, etc.
>> ==============================================
>> To assist you in getting the best answers for FrontPage support see:
>> http://www.net-sites.com/sitebuilder/newsgroups.asp
>>
>> "Clark" <non-(E-Mail Removed)> wrote in message
>> news:lKpjd.44552$(E-Mail Removed)...
>>> So if you upgrade to fp2003, you are requiring your isp to have asp.net to get around snags like
>>> that?
>>>
>>>>See the second part of this KB article:
>>>>http://support.microsoft.com/default...b;en-us;817029
>>>>
>>>>
>>>
>>
>>
>
>

Hey Tom, I know you're not gonna let up on my learning asp coding, so I
thought I would share my work-around for that problem. I just teamed up
with a young buck (friend of my grandsons) who is doing all the work to
completely automate my next 2 sites. We're going 50 / 50 on whatever
comes out of it

Now get this -- the deal I made with him was I would do the site design,
he would do the asp coding. Well, once he got started he says to me just
let him do it all, it's faster that way. OK says me, I can live with
that. So now I am the site strategist / requirements inputter /
critiquer. You would love this guy, he does ALL his coding by hand
(crazy but hey it works for him)

No need for me to learn asp. It's a wonderful world out there, you gotta
love it. :=)

Thomas A. Rowe wrote:

>No, just learn how to hand code your ASP and not rely on the FP database components.
>
>
>