Issue 13449 - Dbase memo fields displayed as Hex
Summary: Dbase memo fields displayed as Hex
Status: CLOSED DUPLICATE of issue 12318
Alias: None
Product: Base
Classification: Application
Component: code (show other issues)
Version: OOo 1.0.3
Hardware: PC Other OS
: P3 Trivial (vote)
Target Milestone: ---
Assignee: Frank Schönheit
QA Contact: issues@dba
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2003-04-15 10:29 UTC by alex.thurgood
Modified: 2006-05-31 14:29 UTC (History)
2 users (show)

See Also:
Issue Type: DEFECT
Latest Confirmation in: ---
Developer Difficulty: ---


Attachments

Note You need to log in before you can comment on or make changes to this issue.
Description alex.thurgood 2003-04-15 10:29:33 UTC
My dbase memo fields created in StarOffice 5.2 are interpreted as LONGVARCHAR
and show up as hex characters in my French 1.0.3 release. Arrgh !! I thought
this problem only existed in the 1.1 branch. I thought the 1.0.3 fixed more
bugs, and wasn't supposed to included those from the 1.1 development.


The problem does not occur in the English 1.0.2 version I have. I'm doomed or
cursed.

Alex
Comment 1 Frank Schönheit 2003-04-15 13:10:55 UTC
Alex, sorry, I cannot reproduce this with a 1.0.3 (english, freshly
installed, windows). Neither with a dBase file created with StarOffice
5.2, nor with 1.0.2, nor with 1.0.3 itself.
Do you mind trying the english 1.0.3 version, to be sure that it's not
a problem of the localized build?
Comment 2 Frank Schönheit 2003-04-16 07:14:27 UTC
I also cannot reproduce this in the french version :(
Comment 3 alex.thurgood 2003-04-16 08:23:33 UTC
Then I am doomed either to staying with 1.0.2 or retyping the whole of
my memo fields for all of my tables :-((
Comment 4 Frank Schönheit 2003-04-16 08:54:18 UTC
I also tried with the bug case attached to issue 12318, but still no
success :(
Comment 5 Rainer Bielefeld 2003-06-25 11:12:54 UTC
I think this is a DUP of issue 12318

Can someone (reporter) decide this?

Rainer
Comment 6 alex.thurgood 2003-06-25 15:13:08 UTC
Confirmed, setting as DUP, and closing.

Alex

*** This issue has been marked as a duplicate of 12318 ***
Comment 7 Frank Schönheit 2003-07-23 13:32:01 UTC
closing
Comment 8 hans_werner67 2004-02-02 12:54:50 UTC
change subcomponent to 'none'