Thanks for responding! Here's what I've discovered so far (copy of a question I just sent out):



Can session variables work with memo fields in databases, or not? I finally resolved an endless "errors occurred" glitch by first
removing textareas from my form. Every field, including each textarea, had a session variable associated with it. ASP didn't seem to
like associating session variables with textarea input fields in HTML forms.



That deletion seemed to work once or twice (without any errors on-screen), from what I remember, but I still encountered the "errors
occurred" message a number of times. So I then removed the memo field from the database that all the other fields in the online form
were pointing to - and the "errors occurred" message never appeared again! 



This is frustrating for me because I'm trying to develop a personal ads form online. Of course, the ad field in the form (a textarea
input field, of course) is associated with a memo field in the database. 



The book 'Beginning ASP Databases' mentions on p. 618 ('In Search of the Lost Data') that there is some weirdness in dealing with
memo fields - but that's in getting the data back out of the database (via rs.field and rs.value), not in placing the data - such as
a new ad - into the db in the first place.



I'm working with the WROX Classifieds example in Chapter 15 of the 'Beginning Active Server Pages 3.0' book. It's a great example
and is quite similar to what I need. It even uses textareas and memo fields - but on a separate linked page, the "edit and add
items" page (this Classifieds project example is like a mini-eBay; the memo field is 'item description'). 



So, apparently, I can do what I need to have done if I place all the general ad registration info on one page with session
variables. I guess the point in starting out that way - with session variables, I mean - is that the code has to check to see if a
chosen username already exists in the db. Also, it has to carry all variables forward (in the session) right away in case a user
immediately to turn around and edit his or her profile/ad. 



But if I follow their structure, I would be placing the ad field on a separate page that isn't using session variables. (This is how
they set up their "edit items" and "add items" page, as I mentioned.) But that's more branching-out than I'd like. Is there some way
to get the ad field back into the main page?







ASP Databases <asp_databases@p...> wrote:

> What's on line 36? (and lines 25-35)?



Cheers

Ken



----- Original Message -----

From: "Bobbi Ragon" 

To: "ASP Databases" 

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?)

I don't think the session variables have any problems with textarea input

fields.



You say that you got an error on line 36.



I'll ask once more - what is on lines 25-36 of your code?



Cheers

Ken





----- Original Message -----

From: <bkragon@m...>

To: "ASP Databases" <asp_databases@p...>

Cc: <ken@a...>

Sent: Wednesday, October 11, 2000 11:54 PM

Subject: [asp_databases] Re: 'errors occurred'-session variables & memo

fields





> Thanks for responding! Here's what I've discovered so far (copy of a

question I just sent out):

>

> Can session variables work with memo fields in databases, or not? I

finally resolved an endless "errors occurred" glitch by first removing

textareas from my form. Every field, including each textarea, had a session

variable associated with it. ASP didn't seem to like associating session

variables with textarea input fields in HTML forms.

>

> That deletion seemed to work once or twice (without any errors on-screen),

from what I remember, but I still encountered the "errors occurred" message

a number of times. So I then removed the memo field from the database that

all the other fields in the online form were pointing to - and the "errors

occurred" message never appeared again!

>

> This is frustrating for me because I'm trying to develop a personal ads

form online. Of course, the ad field in the form (a textarea input field, of

course) is associated with a memo field in the database.

>

> The book 'Beginning ASP Databases' mentions on p. 618 ('In Search of the

Lost Data') that there is some weirdness in dealing with memo fields - but

that's in getting the data back out of the database (via rs.field and

rs.value), not in placing the data - such as a new ad - into the db in the

first place.

>

> I'm working with the WROX Classifieds example in Chapter 15 of the

'Beginning Active Server Pages 3.0' book. It's a great example and is quite

similar to what I need. It even uses textareas and memo fields - but on a

separate linked page, the "edit and add items" page (this Classifieds

project example is like a mini-eBay; the memo field is 'item description').

>

> So, apparently, I can do what I need to have done if I place all the

general ad registration info on one page with session variables. I guess the

point in starting out that way - with session variables, I mean - is that

the code has to check to see if a chosen username already exists in the db.

Also, it has to carry all variables forward (in the session) right away in

case a user immediately to turn around and edit his or her profile/ad.

>

> But if I follow their structure, I would be placing the ad field on a

separate page that isn't using session variables. (This is how they set up

their "edit items" and "add items" page, as I mentioned.) But that's more

branching-out than I'd like. Is there some way to get the ad field back into

the main page?

>

>

>

> ASP Databases <asp_databases@p...> wrote:

> > What's on line 36? (and lines 25-35)?

>

> Cheers

> Ken