MySQL Update Statement won't work with more than one update field

[J.R. Noe]

Why does this not work? If I remove all the fields except one, it will work, but not with more than one field.

function UpdateVials as c (e as p)
dim cn as sql::Connection
dim args as sql::Arguments
dim vSql as c = <<%longstring%
UPDATE narcx_ordervials
SET InitialLoc =:vInitialLoc
InitialLocText =:vInitialLocText
WHERE OrderID =:vOrderID
%longstring%

args.add("vInitialLoc", e.datasubmitted.default_initialloc)
args.add("vInitialLocText", e.datasubmitted.default_initialloctext)
args.add("vOrderID", e.datasubmitted.ID)
cn.open("::Name::CONN")

if cn.execute(vSql,args) = .f.
UpdateVials = "alert('Could not update records.');"
exit function
cn.close()
end if
dim rowsUpdated as n
rowsUpdated=cn.CallResult.rowsAffected
cn.Close()

end function

[RichCPT]

Re: MySQL Update Statement won't work with more than one update field

missing comma between field expressions for the "SET" statement.

[J.R. Noe]

Re: MySQL Update Statement won't work with more than one update field

Ahhhh! Its always the little things. Thank you Rich.
One more question. If I include a date field in the same manner, it causes it to error and will not update any of the fields. Is there something different that needs to be done if the field is a date field?

[RichCPT]

Re: MySQL Update Statement won't work with more than one update field

When you add the date field to the arguments I would make sure it is being added as a character type field. What I do is go into the debugger and use "typeof(e.datasubmitted.somefield)" to see what field type you are working with, look at the value "e.datasubmitted.somefield" and then try convert() or a date formatting function to format that date as a character string to use in the add.arguments method. If you are working across international borders then I do not know how you deal with the changing date format of day first or month first in the date string.

[J.R. Noe]

Re: MySQL Update Statement won't work with more than one update field

Got it. It was apparently a format issue difference between the server and the field. All seems to be working good now. Thank you Rich.