Issue 70151 - database explorer need to select address_query again by mailmerge printing
Summary: database explorer need to select address_query again by mailmerge printing
Status: CLOSED FIXED
Alias: None
Product: Writer
Classification: Application
Component: ui (show other issues)
Version: current
Hardware: All All
: P3 Trivial with 4 votes (vote)
Target Milestone: 4.0.0
Assignee: Ariel Constenla-Haile
QA Contact: issues@sw
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2006-10-06 12:06 UTC by h.ilter
Modified: 2017-05-20 10:32 UTC (History)
3 users (show)

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

Attachments
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this issue.
Description h.ilter 2006-10-06 12:06:17 UTC 
- Create a query from your current database
- Insert fields from the query into a writer document
- Click on print button and answer mailmerge print with Yes.
-> The mailmerge dialog will appear without selected source of the defined query
Note: It works when you use the database instead the query.
Comment 1 Martin Hollmichel 2007-09-10 13:35:54 UTC 
move target to 3.x according http://wiki.services.openoffice.org/wiki/Target_3x
Comment 2 colebantam 2008-03-19 10:00:57 UTC 
Is this (realy anoying) problem indeed so hard to fix, that it must be 
postponed to 3.x?
Comment 3 Starsearcher 2012-09-26 21:59:48 UTC 
Not just annoying - essential for non-IT literate users of a database system - they don't have a clue about 'data sources' - they just wonder why they are not able to print a sheet of labels!
Comment 4 Ariel Constenla-Haile 2012-09-27 01:39:35 UTC 
Root cause:

SwNewDBMgr::ExecuteFormLetter() tries to convert the css.sdb.CommandType from css.uno.Any to sal_Int16, conversion fails because IDL long is mapped to sal_Int32
Comment 5 Ariel Constenla-Haile 2012-09-27 01:45:41 UTC 
Fixed in trunk with revision 1390434
Comment 6 Ariel Constenla-Haile 2012-09-27 01:49:52 UTC 
(In reply to comment #5)
> Fixed in trunk with revision 1390434

Correction: Revision 1390801
(it seems the bugzilla bot is not working)