Hard Returns in Access

[Casey]

I am using ADO in Word 2002 to update a Memo field in an
Access 2002 database. I also have a Data Access Page
which reads the data. When hard returns are saved in the
database, they show up as squares and some chars that you
can't see. They display properly in the DAP, but if the
user in any way sets the focus to one of the bound
textboxes (i.e., clicking on it); the following error
appears:

"A value could not be saved into the datasource's
<fieldname> field. The Operation was cancelled."

There is a KB article # 295213 that talks about the error,
but only for evaluated expressions.
Please help.

:struggling way past my deadline!:

 

[Tim Ferguson]

I am using ADO in Word 2002 to update a Memo field in an
Access 2002 database. I also have a Data Access Page
which reads the data. When hard returns are saved in the
database, they show up as squares and some chars that you
can't see. They display properly in the DAP, but if the
user in any way sets the focus to one of the bound
textboxes (i.e., clicking on it); the following error
appears:

Sounds like Word formatting codes. How are you getting the text from Word
into Jet? The Range.Text property should return nothing but ASCII, and that
should display fine in anything.

Paragraph marks (= hard returns?) would, at a guess, be returned as CR LF,
which is MS-DOS standard. Any PC app should recognise that easily enough,
although transferring to Macs or Unix may cause difficulties with ignorant
applications.

If you have a handy hex editor, transfer some of the text into it and
examine the individual codes. You can probably get more specific help in
the m.p.Word.VBAProgramming groups.

Hope that helps.

Tim F

 

[Guest]

-----Original Message-----


Sounds like Word formatting codes. How are you getting the text from Word
into Jet? The Range.Text property should return nothing but ASCII, and that
should display fine in anything.

Paragraph marks (= hard returns?) would, at a guess, be returned as CR LF,
which is MS-DOS standard. Any PC app should recognise that easily enough,
although transferring to Macs or Unix may cause difficulties with ignorant
applications.

If you have a handy hex editor, transfer some of the text into it and
examine the individual codes. You can probably get more specific help in
the m.p.Word.VBAProgramming groups.

Hope that helps.

Tim F

Thanks for your response. The page displays just fine and
navigates to through the records just fine; unless the
user clicks on one of the TEXTAREA fields bound to the
data. There is only a SELECT Query associated with MSODC
object. Why is it trying to update when I'm using a
snapshot?

 

[Tim Ferguson]

Thanks for your response. The page displays just fine and navigates
to through the records just fine; unless the user clicks on one of the
TEXTAREA fields bound to the data.

I don't think that I was even trying to address any navigation problems.
You were talking about codes within the memo field, and how they were
displaying in a text box on the web page...

There is only a SELECT Query associated with MSODC object. Why is it
trying to update when I'm using a snapshot?

I have no idea: what makes you think anything is being updated?

By the way: can you answer this, which is where I guess the problem is
coming from -


B wishes


Tim F

 

[david epsom dot com dot au]

There is only a SELECT Query associated with MSODC object.
When you click on one of the memo fields, it gets reformatted
for display, which modifies the text because Access can't
handle something (although a hard carriage return should not
cause trouble by itself)

Of course you can't modify the text: it is bound to a
snapshot. So you get a failure message.

(david)

Thanks for your response. The page displays just fine and navigates
to through the records just fine; unless the user clicks on one of the
TEXTAREA fields bound to the data.

I don't think that I was even trying to address any navigation problems.
You were talking about codes within the memo field, and how they were
displaying in a text box on the web page...

There is only a SELECT Query associated with MSODC object. Why is it
trying to update when I'm using a snapshot?

I have no idea: what makes you think anything is being updated?

By the way: can you answer this, which is where I guess the problem is
coming from -


B wishes


Tim F
[/QUOTE]