On 11 Aug 2005 at 22:05, Doug Thompson wrote:
> Maybe I'm missing something, but could use more help please! Thanks.
> >
>
> Generating a document (file) per database record is exactly the way mail
> merge is supposed to work. The objective is to create multiple tailored
> copies of a document
Bottom Post
mike scott wrote:
On 9 Aug 2005 at 10:08, Doug Thompson wrote:
...
8< (snip)
OK, I've had a chance to play around, after reading the document you
suggested. It does look as though OOo goes some way to doing this, but
there do seem to be some problems - either something's n
On 9 Aug 2005 at 10:08, Doug Thompson wrote:
...
> > I like OOo very much, don't get me wrong. But I get very frustrated
> > with problems like this that have no good workaround.
> >
>
> You can create templates that can be reused each time you want to use
> mail merge. That way, you only have
mike scott wrote:
On 8 Aug 2005 at 8:54, Doug Thompson wrote:
Vaughn L. Reid III wrote:
The issue of blank fields in mail merges has been raised several times
in issuezilla since version 1.0.3, but it keeps getting reclassified as
an enhancement. I have to disagree that this is an enhancem
On 8 Aug 2005 at 8:54, Doug Thompson wrote:
> Vaughn L. Reid III wrote:
> >
> > The issue of blank fields in mail merges has been raised several times
> > in issuezilla since version 1.0.3, but it keeps getting reclassified as
> > an enhancement. I have to disagree that this is an enhancement.
On Mon, 2005-08-08 at 07:10 -0500, Vaughn L. Reid III wrote:
> The issue of blank fields in mail merges has been raised several times
> in issuezilla since version 1.0.3, but it keeps getting reclassified as
> an enhancement. I have to disagree that this is an enhancement. The
> functionality
Vaughn L. Reid III wrote:
The issue of blank fields in mail merges has been raised several times
in issuezilla since version 1.0.3, but it keeps getting reclassified as
an enhancement. I have to disagree that this is an enhancement. The
functionality of a properly working and usable mail me
The issue of blank fields in mail merges has been raised several times
in issuezilla since version 1.0.3, but it keeps getting reclassified as
an enhancement. I have to disagree that this is an enhancement. The
functionality of a properly working and usable mail merge is an
essential compon
On 7 Aug 2005 at 6:32, Vaughn L. Reid III wrote:
> One of the crucial usability features that OpenOffice lacks is the
> ability to automatically suppress blank lines caused by empty fields in
> a mail merge.
While that would be useful, it would seem better to fix a more general
problem if it'
Vaughn L. Reid III wrote:
One of the crucial usability features that OpenOffice lacks is the
ability to automatically suppress blank lines caused by empty fields in
a mail merge.
This issue has been submitted several times in issuezilla, but has not
been given priority by the developers. This
10 matches
Mail list logo
