Saving Data problem

Post Reply
brian18
Posts: 23
Joined: Mon Jan 29, 2001 10:18 am

Saving Data problem

Post by brian18 »

I have a form with a textarea field which can contain multiple k of data. When I hit submit and try to save the data to the database, the data is saved, but the page comes up with a "Page cannot be displayed" error message. It seems to happen at about 26k or 27k of data. I would think that it is a limit in HTML, but the data is saved. Can you think of any reason why this would occur and how to fix it? Thanks for any help you can provide.
User avatar
mark
Site Admin
Posts: 5519
Joined: Tue Apr 25, 2000 6:56 pm

Saving Data problem

Post by mark »

I assume that message is from your web browser. What browser are you using? Have tried a different one? What are you trying to display on the page that says "Page cannot be displayed"?
User avatar
John
Site Admin
Posts: 2622
Joined: Mon Apr 24, 2000 3:18 pm
Location: Cleveland, OH
Contact:

Saving Data problem

Post by John »

If all the data is being saved then it appears that the POST is working correctly. What is supposed to be on the result page? Do you get more details on the "Page cannot be displayed"? You might check both the webserver and vortex error logs, but it's possible, especially if you are on a slow connection, that the webserver has a timeout limit for a single connection that you might be exceeding.
John Turnbull
Thunderstone Software
brian18
Posts: 23
Joined: Mon Jan 29, 2001 10:18 am

Saving Data problem

Post by brian18 »

I'm using the most recent IE browser. It is the generic IE "Page Cannot Be Diaplyed" browser message. I checked the vortex logs and there's no error. I was thinking it may be a time out, but it's only taking less than a second to do the insert. The info displayed on the results page is just a confirmation message that the information was displayed and a menu. I'll play around with the time out idea.
User avatar
mark
Site Admin
Posts: 5519
Joined: Tue Apr 25, 2000 6:56 pm

Saving Data problem

Post by mark »

Also turn off IE's "friendly" error messages. They hide the real messages that developers need to see.
Post Reply