JET Database Engine error '80040e14'

[David]

I've got a query command that is checking a field name against it's value.
The query is pulling from an Access 2000 DB. Here's the script:

dsn="Provider=Microsoft.Jet.OLEDB.4.0;Data Source=<physical path to DB on
server>"
Set cnnCIData = Server.CreateObject("ADODB.Connection")
cnnCIData.Open dsn

sqlTrends = "SELECT per,perDisplay FROM trends WHERE " & strAliasT & " = yes
ORDER BY id DESC "
Set rstTrends = cnnCIData.Execute(sqlTrends)

===========================
HERE'S THE PROBLEM:
When strAlias is a value that does not start with a number (i.e. - dog),
then the query executes just fine. When strAlias does start with a number
(i.e. - 123dog) then I get the folling error:

Microsoft JET Database Engine error '80040e14'
Syntax error in query expression '123dog = yes'.
===========================

Why is this happening only when strAlias starts with a number?? I'm
confused. Perhaps someone can suggest to me a better way to compose my
query. Anything is appreciated. Thanks.

[Aaron Bertrand - MVP]

Why does your column name begin with a number???

Try

sqlTrends = "SELECT per,perDisplay FROM trends WHERE [" & strAliasT & "] =
yes ORDER BY id DESC "

[David]

Thanks, that seemed to do the trick.

Is it not good practice to have column names that start with numbers?

"Aaron Bertrand - MVP" <aaron@TRASHaspfaq.com> wrote in message
news:e9GsrVjoDHA.2404@TK2MSFTNGP12.phx.gbl...

> Why does your column name begin with a number???
>
> Try
>
> sqlTrends = "SELECT per,perDisplay FROM trends WHERE [" & strAliasT & "] =
> yes ORDER BY id DESC "
>
>

[Aaron Bertrand - MVP]

> Is it not good practice to have column names that start with numbers?

No. Too much ambiguity.