Sql statement not working

[hifive]

It seems that there is an error in my sql statement, here is the message that ot gave....can someone find the problem...
_______________________________________________

This is the result++

UPDATE nouvelle SET date='fdsdf',title='sdfsd',contents='sdfsdf' WHERE nbnews='57'

Microsoft OLE DB Provider for ODBC Drivers error '80040e14'

[Microsoft][ODBC Microsoft Access Driver] Syntax error in UPDATE statement.


______________________

thank's

/admin/donenews57.asp, line 33

 

[scotth4v]

May be a datatype error, try losing the single quotes on non-strings, etc.

That's my only suggestion, the rest looks liek it should work.

 

[Gamera9]

How about:

UPDATE nouvelle (date,title,contents) SET ('fdsdf','sdfsd','sdfsdf') WHERE nbnews='57';

I agree completely with the single quote idea.

 

[Gamera9]

Sorry - I said I agree with the single quote idea and I put the quotes there anyway. If nbnews is a number field then I would say:
UPDATE nouvelle (date,title,contents) SET ('fdsdf','sdfsd','sdfsdf') WHERE nbnews=57;

 

[jonscott8]

MTL, the problem is you named a field date, which is probably a reserved word. Try:

UPDATE nouvelle T1 SET T1.[date]='fdsdf', T1.title='sdfsd', T1.contents='sdfsdf' WHERE T1.nbnews='57'

AFA the quotes, if the field types are text, they are necessary.

UPDATE nouvelle (date,title,contents) SET ('fdsdf','sdfsd','sdfsdf')

I imagine this would be the result if an UPDATE & INSERT query had an offspring. LOL

It has the structure of an Insert query:
INSERT TableName (field1,field2) VALUES(value1,value2)
but the commands of an Update query:
UPDATE TableName SET field1=value1, field2=value2 Jon Hawkins

 

[Gamera9]

Well ok. I screwed that up; i don't know what I was thinking. I actually know SQL but it certainly isn't evident from my two posts here. Laugh away.

 

[GlennBSI]

Syntax errors aside, aren't you supposed to delimit date fields with # when using Access databases?

ie. ..."Datefield = #" & mydatefield & "#"

 

[Gamera99]

Well that's a good question. My example, such as it was, was supposed to be for Oracle; and it doesn't use the "#" escape character for dates (that I have ever seen). Formatting dates for Oracle is tricky and usually requires some TOCHAR() finagling to get it in a format that Oracle will accept.

 

[GlennBSI]

I've been going against SQL Server for so long, I'm not sure about Access anymore, but it used to be that way. As for Oracle, I do remember it being tricky with all that TOCHAR or TODATE stuff.