Description: When trying to print out images direct from a DB with a query only the first Image is show and repeated in the image control for all other rows while the other fields change correctly. A form generated from the DB will behave correctly with the same settings in the image control Steps to Reproduce: 1.Create a DB. Can be Embedded or remote. Create a Table called LOGOS with 3 Fields. ID. Int Autovalue, IMAGE, VARBINARYIMAGE, NAME, VARCHAR. 2. Create Query for the Table QueryLOGOS. 3. Create a Form from the Query and populate the DB with an IMAGE and a NAME 4. Save DB 5. Create a Writer Document and link it to the DB-Query via the Dataview. 6. Add fields from the Query for ID and NAME. Add an Image control and Link that to IMAGE in the query. 7. Save Document 8. Print docuemnt. It will ask to mail merge say yes. Save as a single file. Actual Results: The first logo in the query is repeated for all entries while the fields update correctly. Expected Results: The image should change as the fields do Reproducible: Always User Profile Reset: No OpenGL enabled: Yes Additional Info: There needs to be a better way to debug such issues. Perhaps some sort of sanity check if the options are not what they are supposed to be.
Created attachment 143127 [details] Output Document This is the output doc
Created attachment 143128 [details] Document Template Template Document to generate Mailmerge document.
The example db file can be found at this link. https://www.file-upload.com/et5kznil7c2e
Created attachment 143153 [details] LogoTest Database The sameple Database.
First, you aren't doing what you think you are doing, I think. As you saw mail merge fields do not include image fields. The two mail merge fields and the three individual image controls are not linked to each other in any way. The fact that the two types of items (fields and controls) are from the same datasource is of no relevance. If you want to do just what you want to do there is a totally different way to go. Create a report in Base.
(In reply to Drew Jensen from comment #5) > If you want to do just what you want to do there is a totally different way > to go. Create a report in Base. Debug: are you happy with this answer?
> Debug: are you happy with this answer? Not especially. Base reports don't allow page size restrictions in the same way that Documents does. That is to say I am trying to print out on an industrial label printer and it will not let me set zero margins nor let me make sure the text lines are x far apart to fit in constricted space. As it is not I have to print the Document as a PDF form and let people fill out what they need by hand before printing out. Not ideal.
(In reply to debug@roosoft.ltd.uk from comment #7) > > Debug: are you happy with this answer? > > Not especially. Base reports don't allow page size restrictions in the same > way that Documents does. That is to say I am trying to print out on an > industrial label printer and it will not let me set zero margins nor let me > make sure the text lines are x far apart to fit in constricted space. > > As it is not I have to print the Document as a PDF form and let people fill > out what they need by hand before printing out. > > Not ideal. Well, in the past I used to print product labels on a single wide label printer for ceramics shipment. In that case it also had an image for scanning and text, what I did is used a base form, which is just a writer file and laid it up in print view. Feed the form from a query with results for the print run, walked down the result set, while print the form for each record. Sounds close to what you want to do.
(In reply to Drew Jensen from comment #8) > (In reply to debug@roosoft.ltd.uk from comment #7) > > > Debug: are you happy with this answer? > > > > Not especially. Base reports don't allow page size restrictions in the same > > way that Documents does. That is to say I am trying to print out on an > > industrial label printer and it will not let me set zero margins nor let me > > make sure the text lines are x far apart to fit in constricted space. > > > > As it is not I have to print the Document as a PDF form and let people fill > > out what they need by hand before printing out. > > > > Not ideal. > > Well, in the past I used to print product labels on a single wide label > printer for ceramics shipment. In that case it also had an image for > scanning and text, what I did is used a base form, which is just a writer > file and laid it up in print view. Feed the form from a query with results > for the print run, walked down the result set, while print the form for each > record. Sounds close to what you want to do. Broadly I suppose. Essentially we have products with different logos that must be attached to them. The labels are just the last part of an auditable printing system I am trying to write. This is because it is to do with food stuffs and so duplicate labels should not be printed unless authorised by someone signing off on that. You don't want today's labels being places on yesterdays good for example. I thought at first it would be pretty easy to just generate a preview in a LO Base form and then print it straight from there, flagging the print as it went. But like I say Base reports are not so easy to work with and trying to constrict them to a concise layout where everything had to be in the same place every time is frustrating to say the least. Maybe if I carry on trying to work on it I can eventually get a template to work but at this stage starting to look like a massively more complex problem and I might need to resign myself to using webforms and php and accessing the DB directly.
> > Maybe if I carry on trying to work on it I can eventually get a template to > work but at this stage starting to look like a massively more complex > problem and I might need to resign myself to using webforms and php and > accessing the DB directly. Actually, I wouldn't mind helping you with this, and can post up an example of what I am talking about, but at this point the conversation should leave the bug tracker and move over ask.libreoffice.org site. Would that work for you?
(In reply to Drew Jensen from comment #10) > > > > Maybe if I carry on trying to work on it I can eventually get a template to > > work but at this stage starting to look like a massively more complex > > problem and I might need to resign myself to using webforms and php and > > accessing the DB directly. > > Actually, I wouldn't mind helping you with this, and can post up an example > of what I am talking about, but at this point the conversation should leave > the bug tracker and move over ask.libreoffice.org site. > > Would that work for you? Yeah I should really. But not sure I have time to write it all down as another post now. Already behind on a PBX I need to set up. Thanks.
@Drew Jensen, should it be closed as RESOLVED NOTABUG ?
(In reply to Xisco Faulí from comment #12) > @Drew Jensen, should it be closed as RESOLVED NOTABUG ? I would think so.