Apache OpenOffice (AOO) Bugzilla – Issue 13497
MS Access memo field CR LF corrupted by OO Text Box
Last modified: 2006-05-31 14:29:06 UTC
When updating MS Access fields using OO Text Box control on a Form, the CR LF is replaced with a LF, which effectively corrupts the memo field. The memo field is not a problem to OO until it is edited. When just viewing the memo field it is displayed correctly. Determining how to handle a memo field in advance would be a difficult programming problem. It occurred to me however that perhaps one work around for this, is to have the Text Box control provide a property which allows the developer to select in the Text Box control how to handle line ends. For example: Enter to insert CR LF or LF. The default could be LF which is what it currently does. Hope this helps. Kelvin
Kelvin, do you access the MS access database via ADO or ODBC? Which version of MS Access did you use to create the database?
I use ODBC version 4.00.6019.00 The MS Access version is MS Access XP. I only use ODBC. No particular reason. It is just that it generally works. I'm happy to extend this testing to ADO as well if necessary.
confirming, grabbing, targeting
accepting
change subcomponent to 'none'
fixed in CWS dba09
for completeness: The behavior encountered here is a bug in the ADO implementation: When *requesting* text from the driver, it is always returned with *unix-like* line ends (which is a line feed character only). When *writing* text, it is completely irritated if you use uni-like line ends - it then corrupts the text. However, when writing DOS-like line ends (carriage return character, followed by a line feed), this is accepted (and funnily returned with unix-like line ends next time you ask for it). A solution is now implemented as described in http://dba.openoffice.org/specifications/forms/multiline_line_ends.sxw (which also fixes issue 14649).
fs->msc: please verify in CWS dba09
verified in CWS dba09
seems to have made it into the master