80040e14 Error

[Chris]

Hi Everyone,

I recently switched from an ODBC driver to the Jet 4.0 OLEDB driver due to
bugs in the ODBC driver. Now I have a problem on my Login page. First let me
say that I compacted the Access DB, and that caused my headaches with the
ODBC driver. The Login page reads 3 tables on loading and displays some
info. This part is still working fine, so I know the connection is okay.
When I enter my login name and password, I get the following error:
Microsoft JET Database Engine error '80040e14'

Syntax error in FROM clause.

/index.asp, line 104

I read the page on this at ASPFAQ.com, but it does not seem to address my
situation. It discusses using reserved words in the table or sending an INT
to a STRING var. Neither is my case. This was working fine with the ODBC
driver, but is now broken. I'm using Dreamweaver MX 2004 and its built-in
Login routine. So, the FROM clause is from DW, and I checked its live value
using .NET and the SELECT statement looks fine:

"SELECT name, pword,rights FROM Password WHERE name='cat' AND pword='p'"

(This line is cut and pasted directly from the .NET debugger.)

My production server is still using the ODBC driver, and when I upload the
compacted DB to it and test it, I get:
Microsoft OLE DB Provider for ODBC Drivers error '80040e10'

[Microsoft][ODBC Microsoft Access Driver] Too few parameters. Expected 1.

/index.asp, line 104

When I restore the original DB (without compacting), then it works fine,
and I get logged into the site. I checked the permissions on the folder and
the DB, but they look okay, and the Login page is accessing the DB to
display the first 3 pieces of info.

I really don't understand this. Any thoughts?? Thanks in advance!

Cheers,
Chris
Dev Env: Win2k - P4; IIS 5; 1G RAM; Access 2000; Connectionless connection
string (no DSN)

[Ray at]

I'll guess that it's a reserved word issue. Try:

"SELECT [name], [pword],[rights] FROM [Password] WHERE [name]='cat' AND
[pword]='p'"

Take a look here, [url]http://www.aspfaq.com/2080[/url], and you'll see that NAME is a
reserved word.

Ray at home

"Chris" <postonly@aol.com> wrote in message
news:u94N3R1pDHA.2404@TK2MSFTNGP12.phx.gbl...

>
> Syntax error in FROM clause.
>
> /index.asp, line 104
>
>
> "SELECT name, pword,rights FROM Password WHERE name='cat' AND pword='p'"
>

[Bob Barrows]

Ray at <%=sLocation%> wrote:

> I'll guess that it's a reserved word issue. Try:
>
> "SELECT [name], [pword],[rights] FROM [Password] WHERE [name]='cat'
> AND [pword]='p'"
>
> Take a look here, [url]http://www.aspfaq.com/2080[/url], and you'll see that
> NAME is a reserved word.
>

"Password" also.

To the OP, reserved words should be avoided for your table and column names.
While Ray's recommended solution of using brackets around the reserved words
will work, you will be better off in the long run simply changing the names
of this table and column.

Bob Barrows


--
Microsoft MVP - ASP/ASP.NET
Please reply to the newsgroup. This email account is my spam trap so I
don't check it very often. If you must reply off-line, then remove the
"NO SPAM"

[Chris]

That was it. That will teach me to read the reserved word list so quickly!
ha! Thank you both for replying. I decided to change the table name and the
field name.

Cheers,
Chris

"Bob Barrows" <reb01501@NOyahoo.SPAMcom> wrote in message
news:etlLSG4pDHA.1740@TK2MSFTNGP12.phx.gbl...

> Ray at <%=sLocation%> wrote:

> > I'll guess that it's a reserved word issue. Try:
> >
> > "SELECT [name], [pword],[rights] FROM [Password] WHERE [name]='cat'
> > AND [pword]='p'"
> >
> > Take a look here, [url]http://www.aspfaq.com/2080[/url], and you'll see that
> > NAME is a reserved word.
> >

>
> "Password" also.
>
> To the OP, reserved words should be avoided for your table and column

names.

> While Ray's recommended solution of using brackets around the reserved

words

> will work, you will be better off in the long run simply changing the

names

> of this table and column.
>
> Bob Barrows
>
>
> --
> Microsoft MVP - ASP/ASP.NET
> Please reply to the newsgroup. This email account is my spam trap so I
> don't check it very often. If you must reply off-line, then remove the
> "NO SPAM"
>
>