Re: Update Table statement causing error

Tech-Archive recommends: Fix windows errors by optimizing your registry

From: David Wier (dwier_at_nospamASPNet101.com)
Date: 10/29/04 

Date: Fri, 29 Oct 2004 13:04:47 -0500

I know 'size' is an ODBC reserved keyword
It's always best to NOT create field or table names from reserved keywords,
however, as you've found, surrounding them with square brackets in your SQL
statements is how to get around it, when you already have them in place.

David Wier
MCP, MVP ASP.NET, ASPInsider
http://aspnet101.com
http://aspexpress.com

"David Phelan" <dphelan@nopitmanspam.com> wrote in message
news:Xns955F9BFEF992Fdphelanpitmancom@216.128.74.129...
> Well, although there was no problem on the insert statement, for whatever
> reason, I applied your suggestion to the update statement and it fixed the
> problem. Thank you very much, I hadn't event thought about reserved words.
>
> Dave
>
>
> "Veign" <NOSPAMinveign@veign.com> wrote in
> news:#SF5ZxplEHA.3912@TK2MSFTNGP12.phx.gbl:
>
> > Try changing this:
> > "insert into tblfiles (filename,path,type,size,created,modified)
> >
> > to this
> > "insert into tblfiles
> > (filename,[path],[type],[size],[created],[modified])
> >
> > As I think you are using field names that are reserved words (type and
> > size). I surrounded others with the [] just to fully test.
> >
>