[This topic is migrated from our old forums. The original author name has been removed]
I've recently figured out how to export multiple result sets to a single Excel file as separate tabs (very handy!). Please consider adding the ability to supply a name for the spreadsheet tab, both in the Export dialog and as an "@Export set" parameter ("ExcelTabName" perhaps).
Hi Steve,
I will open a new feature request ticket.
Thanks.
Regards
Roger
a
anonymous
said
almost 10 years ago
[This reply is migrated from our old forums. The original author name has been removed]
Re: Custom tab name for Excel export
In the new DbVisualizer 9.2 it's possible to change the name of a resultset with the new client-side command:
*@set resultset name <name>*
... but this is not retained when exporting to an Excel spreadsheet. Could the custom resultset names be used for exported spreadsheet tab labels rather than introducing another client-side command?
Roger Bjärevall
said
almost 10 years ago
[This reply is migrated from our old forums.]
Re: Custom tab name for Excel export
Steve,
We will look into this for an upcoming maintenance release.
Regards
Roger
a
anonymous
said
almost 10 years ago
[This reply is migrated from our old forums. The original author name has been removed]
Re: Custom tab name for Excel export
I noticed that this was added in today's 9.2.1 update and just had to try it out straightaway. Works great!
Love it !!!!
a
anonymous
said
over 9 years ago
[This reply is migrated from our old forums. The original author name has been removed]
Re: Custom tab name for Excel export
Hi Steve,
The new feature for resultset name seem not consistent with the other @export options.
Consider the following sample:
@export on;
@export set Filename="Report.xls" Format="XLS" AppendFile="True" ExcelFileFormat="ooxml";
@export set ExcelTitle="Sample Output";
{color:#0000FF}
@set resultset name Sample Report 1 ;{color}
select now() TODAY;
{color:#FF0000}
@set resultset name "Sample Report 2";{color}
select now() TODAY;
@export off;
The first generates a sheet called "Sample Report 1" - whilst the second generates a sheet called " "Sample Report 2"" (including the double quotes ).
Looking at the rest of the @export options, the second one seem more "consistent" in terms of using quoted paramaters.
Any thoughts on this?
BTW, is this feature meant to replace the current "@export set TableName" feature when exporting to named sheets?
Thanks again to the dev teams and keep up the good work!
Regards,
Ricky
Edited by: Ricky Banaag on Mar 11, 2015 9:27 AM
Edited by: Ricky Banaag on Mar 11, 2015 9:27 AM
Roger Bjärevall
said
over 9 years ago
[This reply is migrated from our old forums.]
Re: Custom tab name for Excel export
Ricky,
For @export there are a lot of parameters while for @set resultset name and @echo these are single operation commands. That is the reason no quotes are needed for the latter ones.
Naming sheets can be accomplished by the following, in order:
- @export set ExcelSheetName="x"
- @set resultset name x;
- @export set TableName="x"
default without any of these is current table name (if it can be retrieved)
I suggest you use ExcelSheetName to name the sheets. The @set resultset name is also useful as it names the result set tabs and any sheets in an Excel export.
Regards
Roger
anonymous