Dazed and Confused....

Hi.

I'm using an Access 2002 DB and ASP. For the purposes of this post, the
simplied SQL statement in question is:

UPDATE dbtable SET status=" & xstat (xstat is yes/no)

The exact same code works just fine on at least a dozen different
servers in the US. It's part of a common function I use all the time.

I have a client in Brazil . When they run this code their server throws
an error...

Microsoft JET Database Engine erro '80040e10'
Nenhum valor foi fornecido para um ou mais parâmetros necessários.
(No value given for one or more necessary parameters)

BUT, I'm 100% certain that the field names and types are correct, and as
I said above, this code works fine on many servers in the US

If I hardcode: UPDATE dbtable SET status=True... it works fine.

If I hardcode:
xstat=True
SQLx="UPDATE dbtable SET status=" & xstat
response.write SQLx

The code fails with the error I mentioned... and the SQLx string looks
like: UPDATE dbtable SET status =Verdadeiro (which means True in
Brazilian)

Go figure. Any ideas what I must do to have the Engine/database
recognize the foreign language equivalent of True?

Tim

--
Posted via http://dbforums.com

|{evin
Sun Jul 27 22:50:55 CDT 2003

On Mon, 28 Jul 2003 02:58:26 +0000, MrWizard
<member27104@dbforums.com> wrote:

>
>Hi.
>
>I'm using an Access 2002 DB and ASP. For the purposes of this post, the
>simplied SQL statement in question is:
>
>UPDATE dbtable SET status=" & xstat (xstat is yes/no)
>
>The exact same code works just fine on at least a dozen different
>servers in the US. It's part of a common function I use all the time.
>
>I have a client in Brazil . When they run this code their server throws
>an error...
>
>Microsoft JET Database Engine erro '80040e10'
>Nenhum valor foi fornecido para um ou mais parâmetros necessários.
>(No value given for one or more necessary parameters)
>
>BUT, I'm 100% certain that the field names and types are correct, and as
>I said above, this code works fine on many servers in the US
>
>If I hardcode: UPDATE dbtable SET status=True... it works fine.
>
>If I hardcode:
>xstat=True
>SQLx="UPDATE dbtable SET status=" & xstat
>response.write SQLx
>
>The code fails with the error I mentioned... and the SQLx string looks
>like: UPDATE dbtable SET status =Verdadeiro (which means True in
>Brazilian)
>
>Go figure. Any ideas what I must do to have the Engine/database
>recognize the foreign language equivalent of True?
>
>Tim

Have you tried:

SQLx = "UPDATE dbtable SET status='" & xstat & "'"

Note the added 's

Ray
Sun Jul 27 22:51:16 CDT 2003

Set xstat to 1 so you don't have to worry about language symantecs.


xstat=1
SQLx = "UPDATE dbtable SET status=" & xstat

Also, when in doubt, stick your table and column names in [], like:

SQLx = "UPDATE [dbtable] SET [status]=" & xstat

to rule out any issues with reserved words.

Ray at home

--
Will trade ASP help for SQL Server help


"MrWizard" <member27104@dbforums.com> wrote in message
news:3154967.1059361106@dbforums.com...
>
> Hi.
>
> I'm using an Access 2002 DB and ASP. For the purposes of this post, the
> simplied SQL statement in question is:
>
> UPDATE dbtable SET status=" & xstat (xstat is yes/no)
>
> The exact same code works just fine on at least a dozen different
> servers in the US. It's part of a common function I use all the time.
>
> I have a client in Brazil . When they run this code their server throws
> an error...
>
> Microsoft JET Database Engine erro '80040e10'
> Nenhum valor foi fornecido para um ou mais parâmetros necessários.
> (No value given for one or more necessary parameters)
>
> BUT, I'm 100% certain that the field names and types are correct, and as
> I said above, this code works fine on many servers in the US
>
> If I hardcode: UPDATE dbtable SET status=True... it works fine.
>
> If I hardcode:
> xstat=True
> SQLx="UPDATE dbtable SET status=" & xstat
> response.write SQLx
>

MrWizard
Mon Jul 28 01:09:34 CDT 2003


I was looking for a Session.LCID type solution... but I'll try that!

--
Posted via http://dbforums.com