Apache OpenOffice (AOO) Bugzilla – Issue 12019
Field codes shown in table that should be displayed as text
Last modified: 2013-08-07 14:38:26 UTC
I'll attach an MS Word document presumably authored in MS Word. The third page contains a table of values, some of which come from a database of some sort. Using Word these fields display as field values. Using OpenOffice.org writer 643 or 1.01 under Linux, and 1.0 under Windows, the values are not displayed. Instead, what appear to be field codes are displayed, no matter if View / Fields is selected or not (this does have an effect in modifying what is displayed, but the user values are not displayed). Thanks and best wishes, Damon
Created attachment 4970 [details] MS Word document that shows bug with displaying tables
Damon, thank you for using and supporting OOo. Duplicated on RH 9.0, OOo 1.0.3.1 & 1.1 Beta 2. Duplicated on WinNT 4.0 SP6a, OOo 1.0.3.1. Summary Is this a bug or an enhancement request? OOo is probably doing the right thing, since it doesn't have the original data source that was used to merge the data into the table on page 3. However, it looks like MS Word is reading some sort of cache inside the Word doc that contains the values inserted into the fields from the last merge operation. In Word, if you "Update Field" for any of the fields in the table on page 3, you will get the same result as OOo since Word doesn't have the original data source either.
Reassigned to MRU.
This is an enhancement request. As long as the database connection has VERY different handling in Word and OO Writer, this will not be possible to solve by a little filter fix (or hack). For access to a database table it needs to be applied in OO's database settings. The importer won't know the database and so there must be a kind of automated process started, which checks the availability of the database and than adds the database to OO's settings (with a suitable name). These info's than have to be handed back to the import filter.
Considered for 'Office later'.
To grep the issues easier via "requirements" I put the issues currently lying on my owner to the owner "requirements".