Freelancers Network
 
skill list top cap
Homepage
Join the Freelancer's Network
Update your details
Find a freelancer
Post a project
Find a project
Projects Archive
Post a job
Find a job
Jobs Archive
See Dan's Pages
See Andy's Pages
Link to this site
Resources
Join/Leave Forum
Forum Messages
+Additions+ Adverts
Advertising
Contact Us
Subscribe to our newsletter - enter your email address and hit return
Freelancers.net is owned and operated by Andy Stowell and Dan Winchester
skill list end cap
guru web hostcom

Find me again on Freelancers.net

FN-FORUM: Updating / inserting a LONGTEXT field in mySQL using ASP / IIS

date posted 15th January 2007 11:11

Hi

I had a table I wanted to update with a LONTEXT field using the ADO
Update method. When I added a new record it worked fine. When I
updated a record it would cause an error if I lengthened the content
of this field. The error was =85

Error Type:
Microsoft Cursor Engine (0x80004005)
Data provider or other service returned an E_FAIL status.

=85 which I'd never seen before. Googling said it was a provider error
that basically meant it didn't know what was going wrong and you could
not tell much from it. It would update fine if I was shortening the
content. I temporarily solved the problem by just having a record in
the table with very long content for that field. For some reason I
was then always able to update this field with longer content in other
records. Fine =85 a mystery =85 but at least it worked.

However I have now added another LONGTEXT field to this table and it's
again causing problems. So I'm hoping there's some difference in the
way you update these fields when using mySQL as opposed to an MS db.

On my local set up I still sometimes had this error. Sometimes it
worked OK. Other times I'd get this error =85

Error Type:
Microsoft Cursor Engine (0x80040E21)
Multiple-step operation generated errors. Check each status value.
/lifo/administration/content/surveys/processupdatesurvey.asp, line 241

Line 241 is =85

rsSurvey("Introduction") =3D strIntroduction

which I'd then use the ADO update method on. 'Introduction' is one of
my LONGTEXT fields.

So I then decided to use a SQL update just for these two fields that
were causing the problem and it all worked fine locally using =85

strsSQL =3D "UPDATE tblSurveys SET Introduction =3D '" & strIntroduction &
"', Instructions =3D '" & strInstructions & "' WHERE SurveyID =3D " &
strID & ";"


However on my remote server I get this error =85

Microsoft OLE DB Provider for ODBC Drivers error '80040e14'
[MySQL][ODBC 3.51 Driver][mysqld-5.0.27-community-nt]You have an error
in your SQL syntax; check the manual that corresponds to your MySQL
server version for the right syntax to use near 's important to you,
how you get the most out of situations and how you interact ' at line
1
/lifo/administration/content/surveys/processupdatesurvey.asp, line 270

Line 270 is the line after the SQL above and is as follows=85

rsSurvey2.Open strsSQL, strConnect, adOpenForwardOnly,
adLockOptimistic, adCmdText

So can anyone shed some light on why I'm getting all these problems
for LONGTEXT fields? Is there another data type I should be using?

TIA
Paul



Messages by Day
January 31st 2007
January 30th 2007
January 29th 2007
January 28th 2007
January 27th 2007
January 26th 2007
January 25th 2007
January 24th 2007
January 23rd 2007
January 22nd 2007
January 21st 2007
January 20th 2007
January 19th 2007
January 18th 2007
January 17th 2007
January 16th 2007
January 15th 2007
January 14th 2007
January 13th 2007
January 12th 2007
January 11th 2007
January 10th 2007
January 9th 2007
January 8th 2007
January 7th 2007
January 6th 2007
January 5th 2007
January 4th 2007
January 3rd 2007
January 2nd 2007
January 1st 2007


Messages by Month
December 2007
November 2007
October 2007
September 2007
August 2007
July 2007
June 2007
May 2007
April 2007
March 2007
February 2007
January 2007


Messages by Year
2008
2007
2006
2005
2004
2003
2002
2001
2000