Textfield Question

[shimon@iafrica.com]

Does anyone know why the " - quote presents a problem
when updating to a Access DB. I know the single quote '
does.

Shimon

[Aaron Bertrand - MVP]

Can you define "presents a problem" - what problem? An error message? If
so, what is it? Can you show the code in context?

--
Aaron Bertrand
SQL Server MVP
[url]http://www.aspfaq.com/[/url]




"shimon@iafrica.com" <anonymous@discussions.microsoft.com> wrote in message
news:1290401c3c09b$86f3e2e0$a601280a@phx.gbl...

> Does anyone know why the " - quote presents a problem
> when updating to a Access DB. I know the single quote '
> does.
>
> Shimon

[Ray at]

"Roland Hall" <nobody@nowhere> wrote in message
news:Of3xGrOwDHA.1660@TK2MSFTNGP09.phx.gbl...

> "Aaron Bertrand - MVP" wrote:

> > Can you define "presents a problem" - what problem? An error message?

If

> > so, what is it? Can you show the code in context?

>
> Aaron...
>
> I think he's referring to a double quote in the middle of a SQL update
> statement and how it presents a problem.
>
> If customer's name had a double quote in the name. I believe this is what
> he's eluding to.

That's not a problem. THere's nothing wrong with:

INSERT INTO t (c) VALUES ('asd"asdf')

The only place that " will cause a problem will be in the HTML and this is
why one should replace " with &quot; when pulling data from a database and
writing it to an input value, for example.

Ray at work

[Roland Hall]

"Aaron Bertrand - MVP" wrote:

> Can you define "presents a problem" - what problem? An error message? If
> so, what is it? Can you show the code in context?

Aaron...

I think he's referring to a double quote in the middle of a SQL update
statement and how it presents a problem.

If customer's name had a double quote in the name. I believe this is what
he's eluding to.

--
Roland

This information is distributed in the hope that it will be useful, but
without any warranty; without even the implied warranty of merchantability
or fitness for a particular purpose.

[Aaron Bertrand [MVP]]

Why would that cause a problem? And what problem?

--
Aaron Bertrand
SQL Server MVP
[url]http://www.aspfaq.com/[/url]

> I think he's referring to a double quote in the middle of a SQL update
> statement and how it presents a problem.
>
> If customer's name had a double quote in the name. I believe this is what
> he's eluding to.

[Aaron Bertrand [MVP]]

> > Why would that cause a problem? And what problem?

>
> What is this, shoot the messenger?

Who's shooting? And what makes you think my questions are directed solely
at you?

You might expect the original poster to chime in here and clarify, at some
point.

--
Aaron Bertrand
SQL Server MVP
[url]http://www.aspfaq.com/[/url]

[Roland Hall]

"Aaron Bertrand [MVP]" wrote:

> Why would that cause a problem? And what problem?

What is this, shoot the messenger?

[Roland Hall]

"Ray at <%=sLocation%>" wrote:

> "Roland Hall" wrote:

> > "Aaron Bertrand - MVP" wrote:

> > > Can you define "presents a problem" - what problem? An error message?

> If

> > > so, what is it? Can you show the code in context?

> >
> > Aaron...
> >
> > I think he's referring to a double quote in the middle of a SQL update
> > statement and how it presents a problem.
> >
> > If customer's name had a double quote in the name. I believe this is

what

> > he's eluding to.

>
> That's not a problem. THere's nothing wrong with:
>
> INSERT INTO t (c) VALUES ('asd"asdf')
>
> The only place that " will cause a problem will be in the HTML and this is
> why one should replace " with &quot; when pulling data from a database and
> writing it to an input value, for example.

I didn't ask the question. I clarified it.

[Roland Hall]

"Aaron Bertrand [MVP]" wrote:

> > > Why would that cause a problem? And what problem?

> >
> > What is this, shoot the messenger?

>
> Who's shooting? And what makes you think my questions are directed solely
> at you?
>
> You might expect the original poster to chime in here and clarify, at some
> point.

Maybe it's the severe blood loss?!

Yes, it would be nice to hear from the originator but I think he's hidin' in
the weeds.