Hi,
I'm using the default wizard to report (and NOT Report Builder, whose existence I am aware of, but whose use I'd rather leave to others for now).
For what I gathered so far, it seems like I won't be able to by-pass tables in the report template, but I was offered help in editing the format of these tables through macros immediately upon running the report. That was a desirable first step.
But ultimately, I decided tables were not quite what I wanted to use. Using macros again, I can now get rid of the tables, but first, I have to run a Save_as and get the report in ODT format, then copy the macro into the newly formed document, and finally run them. I get the results I want, but it takes a lot (a LOT) of steps, and I would appreciate cutting the number of them.
I see 2 options that would be equally interesting to me, especially if they bear fruits:
The macro that runs the report and configure the tables in it, ...
• ...could potentially transform the tables into text directly in the report.
OR
• ...it could do the Save_as_ODT for me, open that file and run the second part of the macro on it.
If neither is possible, then I would be willing to consider saving the report as an ODT file, but one that would already contain the macro that I use to format it the way I want (a template containing my macro, in short, if my way of wording it was too imprecise). That would save me at least the step of having to copy the macro onto the file...
Reporting to text
Reporting to text
AOO 4 • Windows7
Because many might have tried to come up with an answer to my questions before one succeeded at it...
THANK YOU! to everybody who are trying to solve my Open Office problems, even if fruitlessly.
Because many might have tried to come up with an answer to my questions before one succeeded at it...
THANK YOU! to everybody who are trying to solve my Open Office problems, even if fruitlessly.
Re: Reporting to text
If someone gets an answer, then fine, I'll check it out for sure.
Otherwise, I'm guessing I might have found another way around my problem: fancier queries producing long fields of concatenated data that I could later edit through macros directly in the report.
I'll just have to study SQL a bit.
Sorry for any time I could have had people losing on this.
Otherwise, I'm guessing I might have found another way around my problem: fancier queries producing long fields of concatenated data that I could later edit through macros directly in the report.
I'll just have to study SQL a bit.
Sorry for any time I could have had people losing on this.
AOO 4 • Windows7
Because many might have tried to come up with an answer to my questions before one succeeded at it...
THANK YOU! to everybody who are trying to solve my Open Office problems, even if fruitlessly.
Because many might have tried to come up with an answer to my questions before one succeeded at it...
THANK YOU! to everybody who are trying to solve my Open Office problems, even if fruitlessly.
Re: Reporting to text
Hello!
I'm sorry because of my English. Not only am I a very bad English student, but also I am very bad at programming.
I've just fixed an issue I had about reporting and using textfields. I wanted to justify a text LongVarChar when I use it in a report, and I think I got it.
I don't know if you need this, but I'll attache the example database, but it is made in Spanish language.
I didn't use in this case tables into the report, but I didn't use macros to erase them. I directly erased them when I was desinging and used a new subform into the report, where I made all my job.
You have to notice that they are two reports. The first one ( INFORME ) is a previous job to get a 'Cangrow' field, and I got it for short fields (no longvarchar), but also for long fields (Longvarchar and multiline). Nevertheless the second one (INFORME2) is the most recently job, and I change the final part of the macro in orther no to get a 'Cangrow' textfield. I've just got to copy, and then past into the Writer document which is a Report. to do that I reduced untill no see the field 'Texto1', and put by it a bookmark in order to get the cursor the place to past the text.
I used two macros made by the macros recorder of Writer to justify a text and replace line breaks ( .\n\n are replaced by \n and the second one repeat the search of \n to replace one another time by \n).They are called PonerIntros and PonerIntros2
My English is a problem, but I think is much easier to understand my English than follow this two macros by code.
I hope this is what you need, or it could be useful to our job for other issues
Bye!
I'm sorry because of my English. Not only am I a very bad English student, but also I am very bad at programming.
I've just fixed an issue I had about reporting and using textfields. I wanted to justify a text LongVarChar when I use it in a report, and I think I got it.
I don't know if you need this, but I'll attache the example database, but it is made in Spanish language.
I didn't use in this case tables into the report, but I didn't use macros to erase them. I directly erased them when I was desinging and used a new subform into the report, where I made all my job.
You have to notice that they are two reports. The first one ( INFORME ) is a previous job to get a 'Cangrow' field, and I got it for short fields (no longvarchar), but also for long fields (Longvarchar and multiline). Nevertheless the second one (INFORME2) is the most recently job, and I change the final part of the macro in orther no to get a 'Cangrow' textfield. I've just got to copy, and then past into the Writer document which is a Report. to do that I reduced untill no see the field 'Texto1', and put by it a bookmark in order to get the cursor the place to past the text.
I used two macros made by the macros recorder of Writer to justify a text and replace line breaks ( .\n\n are replaced by \n and the second one repeat the search of \n to replace one another time by \n).They are called PonerIntros and PonerIntros2
My English is a problem, but I think is much easier to understand my English than follow this two macros by code.
I hope this is what you need, or it could be useful to our job for other issues
Bye!
- Attachments
-
- JUSTIFICAR.7z
- (73.81 KiB) Downloaded 189 times
OpenOffice 4.1.5 on Windows 10
LibreOffice 5.1 on Windows 7
LibreOffice 6.0.1 on Windows10
LibreOffice 5.1 on Windows 7
LibreOffice 6.0.1 on Windows10