|
 |
asp_databases thread: 'errors received' message for functioning process; why?
Message #1 by "Bobbi Ragon" <bkragon@m...> on Tue, 10 Oct 2000 23:02:25 +0100
|
|
I'm developing some coding for a community group and have a question about
a process that is actually working for me (I think) but generates error
messages.
My code is similar to the application 'WROX Classifieds' in Chapter 15 of
the Beginning Active Server Pages 2.0 book. Has anyone worked with that
example code?
After I fill out the form, I get an error message. But if I
hit 'refresh' (or 'reload'), the confirmation page ('thanks for
submitting an ad,' etc.) then appears on the screen as it would
normally.
Also, when I check the database (Access 2000 format), all of the just-
submitted data is always there.
However, if I hit the 'edit profile' link on the confirmation page, I get
my form that's all filled in except for the password field (that's how
it's supposed to work). For some reason, though, the last two fields are
also empty. Those are the fields for ad heading (a text field) and ad (a
memo field, in the db). Of course, as I indicated, they're blank only on
the 'edit profile' page - they already exist as populated fields in the
db.
In Personal Web Server, the error message looks like this:
Microsoft OLE DB Provider for ODBC Drivers error '80040e21'
Errors occurred
/IISSAMPLES/profiles/newuser2.asp, line 36
This is probably because my ODBC driver for Access was just upgraded from
97 to 2000. I don't remember having any glitches up to then, but I'm not
sure.
Also, even on a regular server (where the ODBC driver for Access 2000 has
been working correctly) I get a similar kind of error message:
Microsoft OLE DB Provider for ODBC Drivers error '80040e21'
Multiple-step OLE DB operation generated errors. Check each OLE DB status
value, if available. No work was done.
/testing/newuser2.asp, line 36
So, what's going on with that? The program tracks logins and passwords,
and it seems to be able to do that without a problem.
Could it be (at least partly) because I'm working with ASP 2.0? I can't
upgrade to ASP 3.0 yet because I have Windows 98 at work. (will soon be
able to upgrade at home, though; would that help for this project?)
Message #2 by "Ken Schaefer" <ken@a...> on Wed, 11 Oct 2000 18:11:44 +1000
|
|
What's on line 36? (and lines 25-35)?
Cheers
Ken
----- Original Message -----
From: "Bobbi Ragon" <bkragon@m...>
To: "ASP Databases" <asp_databases@p...>
Sent: Thursday, October 12, 2000 1:16 AM
Subject: [asp_databases] 'errors received' message for functioning process;
why?
> I'm developing some coding for a community group and have a question about
> a process that is actually working for me (I think) but generates error
> messages.
>
> My code is similar to the application 'WROX Classifieds' in Chapter 15 of
> the Beginning Active Server Pages 2.0 book. Has anyone worked with that
> example code?
>
> After I fill out the form, I get an error message. But if I
> hit 'refresh' (or 'reload'), the confirmation page ('thanks for
> submitting an ad,' etc.) then appears on the screen as it would
> normally.
>
> Also, when I check the database (Access 2000 format), all of the just-
> submitted data is always there.
>
> However, if I hit the 'edit profile' link on the confirmation page, I get
> my form that's all filled in except for the password field (that's how
> it's supposed to work). For some reason, though, the last two fields are
> also empty. Those are the fields for ad heading (a text field) and ad (a
> memo field, in the db). Of course, as I indicated, they're blank only on
> the 'edit profile' page - they already exist as populated fields in the
> db.
>
>
> In Personal Web Server, the error message looks like this:
>
> Microsoft OLE DB Provider for ODBC Drivers error '80040e21'
>
> Errors occurred
>
> /IISSAMPLES/profiles/newuser2.asp, line 36
>
>
> This is probably because my ODBC driver for Access was just upgraded from
> 97 to 2000. I don't remember having any glitches up to then, but I'm not
> sure.
>
>
> Also, even on a regular server (where the ODBC driver for Access 2000 has
> been working correctly) I get a similar kind of error message:
>
> Microsoft OLE DB Provider for ODBC Drivers error '80040e21'
>
> Multiple-step OLE DB operation generated errors. Check each OLE DB status
> value, if available. No work was done.
>
> /testing/newuser2.asp, line 36
>
>
> So, what's going on with that? The program tracks logins and passwords,
> and it seems to be able to do that without a problem.
>
> Could it be (at least partly) because I'm working with ASP 2.0? I can't
> upgrade to ASP 3.0 yet because I have Windows 98 at work. (will soon be
> able to upgrade at home, though; would that help for this project?)
|
|
 |