<%
dim A
dim B
dim C
dim D
dim E
dim F
dim G
dim H
dim strdbpath
A = Request.Form("Number")
B = Request.Form("Nickname")
C = Request.Form("Description")
D = Request.Form("Category")
E = Request.Form("AskingPrice")
F = Request.Form("Condition")
G = Request.Form("Sold")
H = Request.Form("OrigID")
strDBPath = Server.MapPath("main_processing.mdb")
Set oConn2 = Server.CreateObject("ADODB.Connection")
oConn2.Open "Provider=Microsoft.Jet.OLEDB.4.0;Data Source=" & strDBPath & ";"
oConn2.Execute ("UPDATE Results SET Number = '222', Nickname = '2222', Description = '22222', Category = '22222', AskingPrice = '2222', Condition = '22222', Sold = '22222' WHERE ID = 2")
%>

This is my code, I always get a "SYNTAX ERROR IN UPDATE QUERY" can somebody please help?

Thanks so much...

Try it without the parenthesis:

oConn2.Execute "UPDATE Results SET Number = '222', Nickname = '2222', Description = '22222', Category = '22222', AskingPrice = '2222', Condition = '22222', Sold = '22222' WHERE ID = 2"

Microsoft JET Database Engine error '80040e14'

Syntax error in UPDATE statement.

/Desk01/dym3.asp, line 58

I'm still getting this error, I'm sure that my SYNTAX is right.

Please Help.

Thanks.

Are all of your columns text columns?

This error sometimes is caused by a table name or field name that is a reserved word. I'm not fully aware of all the reserved words, but to see if this is the cause, try renaming your table and fields and see if that makes any difference. I would start by renaming the table first.

Tim

That's a good point. You can put your tables and columns in brackets [ ] to tell the interpreter not to use them as keywords:

UPDATE [Results] SET [Number] = '222', [Nickname] = '2222', [Description] = '22222', [Category] = '22222', [AskingPrice] = '2222', [Condition] = '22222', [Sold] = '22222' WHERE [ID] = 2

I'll give that a try

Thanks

It ocassionally works, it says operation must use an updatable query?

Can somebody please help me?

MOD EDIT: No need for the abuse. You have been warned.

If it is working sometimes and not working at others I would suggest it has something to do witht eh state of the database or any locks you might have on the tables or the particular record.

Can you give us any idea when it works and when it doesn't work?

At a guess I would say this would fail if the table was open in Access or if you were viewing the record in Access, but should work at all other times.

Access is finicky. Since it was not designed to be a high performance DB, it often has problems with multiple insert/updates that occur simultaneously.