problem with insert into

[koner]

Hi,

I have the following code for inputting the two variables userid and password from the form to my ms access db:

Cn.Execute "INSERT INTO Users (uid,password) Values " & _
"('" & userid & "', '" & pwd & "')"

But it gives the following error:

Microsoft JET Database Engine error '80040e14'

Syntax error in INSERT INTO statement.

/loginms/Register.asp, line 43


Can anyone help with this please?

Thanks very much in advance.

[sashi]

Hi there,

Kindly refer to below modified SQL statement, take care my fren.. :)

  Cn.Execute "INSERT INTO Users (uid,password) Values " & _
  "('" & userid & "','" & pwd & "')"
 

[koner]

Hi there,

Kindly refer to below modified SQL statement, take care my fren.. :)

  Cn.Execute "INSERT INTO Users (uid,password) Values " & _
  "('" & userid & "','" & pwd & "')"
 

Hi again,

Thank you very much for your reply. However, there seems to be a problem with your code as well (it again gives the same syntax error).

Also, to be honest, I could not see a difference with the code I wrote and your version. Am I missing something?

Thank you very much again.

[sashi]

Hi there,

Quotation marks ( "', ‘ ’, “ ” ) are important, check out. Good luck & Take care.

[wyvern67]

I had this same problem using a MS Access Database table. I just left out the column names in my statement and the syntax error went away.

Try this, Cn.Execute "INSERT INTO Users Values " & _
"('" & userid & "', '" & pwd & "')"

My belief right now is that MS Access doesn't like it when you define all of the columns in a table for inserting. I haven't tried yet, but I think that if you had three columns, and defined two in your statement, then the command would work, but if you have two columns, and you define both in your statement, MS Access generates the syntax error you are experiencing.

[avdbrink]

Hi there,

The problem you had was probably caused by Access having some fieldnames as reserved keywords. Try putting [brackets] around your fieldnames and your problem will probably go away, while still using correct transact-sql statements.

Cheers,
Arno

[wyvern67]

Yep. That did it. Brackets fixed it. Thanks!