I have a report with some columns that are visible\invisible based on a
parameter value. The report renders fine in HTML and when exported to Excel.
But when its exported to PDF the report shows blank white space for some of
the columns that are invisible, e.g. the report is 3 pages wide when the
collumns are all visible, it is 1 page wide when some are invisible, but if
you export the 1 page wide report to PDF it still comes out as 3 pages wide,
with the last 2 pages just alll blank space.
ANything I can do?Did you find any solutions? I had teh same problem.
I am setting the visibility for the Rows through the expression. They are
not showing in HTML mode. However, If I export to PDF it shows some white
spaces.
"NH" wrote:
> I have a report with some columns that are visible\invisible based on a
> parameter value. The report renders fine in HTML and when exported to Excel.
> But when its exported to PDF the report shows blank white space for some of
> the columns that are invisible, e.g. the report is 3 pages wide when the
> collumns are all visible, it is 1 page wide when some are invisible, but if
> you export the 1 page wide report to PDF it still comes out as 3 pages wide,
> with the last 2 pages just alll blank space.
> ANything I can do?|||Hi,
No, never found a solution. I am afraid that you dont get many replies to
your queries in this forum.
"GC" wrote:
> Did you find any solutions? I had teh same problem.
> I am setting the visibility for the Rows through the expression. They are
> not showing in HTML mode. However, If I export to PDF it shows some white
> spaces.
>
> "NH" wrote:
> > I have a report with some columns that are visible\invisible based on a
> > parameter value. The report renders fine in HTML and when exported to Excel.
> > But when its exported to PDF the report shows blank white space for some of
> > the columns that are invisible, e.g. the report is 3 pages wide when the
> > collumns are all visible, it is 1 page wide when some are invisible, but if
> > you export the 1 page wide report to PDF it still comes out as 3 pages wide,
> > with the last 2 pages just alll blank space.
> >
> > ANything I can do?|||I have experienced something like this before...the problem is that in
order to shrink up the hidden columns then you will need to set the
visibility property on each column, not just the tablerow. Very
tedious but I believe that this may be what your report needs...
Matt A|||i have a similar problem. html & xls work fine, but when you export to
csv, the columns are hidden no matter what you do...
reportdude wrote:
> I have experienced something like this before...the problem is that in
> order to shrink up the hidden columns then you will need to set the
> visibility property on each column, not just the tablerow. Very
> tedious but I believe that this may be what your report needs...
> Matt A|||Thanks for the Update. I have tried the option of applying the Expression for
the Visibiliy of every cell in that Row. Still it doesn't make any difference.
This is creating space at the end of the Report. ( I have few Sub Reports).
If I set the hidden false then the white spaces are disappearing. However
this works well in HTML Viewer.
"reportdude" wrote:
> I have experienced something like this before...the problem is that in
> order to shrink up the hidden columns then you will need to set the
> visibility property on each column, not just the tablerow. Very
> tedious but I believe that this may be what your report needs...
> Matt A
>
Showing posts with label based. Show all posts
Showing posts with label based. Show all posts
Monday, March 26, 2012
Friday, March 23, 2012
pbm while connecting to a remote server
Hi,
I have a pbm while connecting to the remote SQL server.
Recently we hired one win2003 based Dedicated server and installed SQl
server 2000. I have the sa password and the ip of the server, and when i
connect to this server from my local machine by configuring client n/w
utility, its giving me the error. like SQL server Does not exists ?
What shall i do ? i've disabled the firewall also, but not successful yet.
Also one more problem. The version i've installed is Enterprise Edition, and
will there be any problem if i uninstall it and reinstall the Standard
edition?
Thanking u in advance LaraHi
You should have no problems with un-installing Enterprise Edition and
re-installing Standard if you are not using any of the additional features
that it has. You may want to look at
http://support.microsoft.com/defaul...b;en-us;Q314546 for
transferring logins and dealing with Orphaned users if you have them. Make
sure that the new version is service packed and patched to the same level.
Backing up your database before un-installation will make sure that you have
a safe copy.
When you install the new system make sure that the correct protocols are
listed on the server's server network utilities. Check that you can ping the
server from your client and that the client also has the correct network
protocols. You may want to try SQLPing or SQLRecon to see if the server is
contactable.
John
"lara" <lara@.l.com> wrote in message
news:eOx2EApZFHA.1088@.TK2MSFTNGP14.phx.gbl...
> Hi,
> I have a pbm while connecting to the remote SQL server.
> Recently we hired one win2003 based Dedicated server and installed SQl
> server 2000. I have the sa password and the ip of the server, and when i
> connect to this server from my local machine by configuring client n/w
> utility, its giving me the error. like SQL server Does not exists ?
> What shall i do ? i've disabled the firewall also, but not successful yet.
> Also one more problem. The version i've installed is Enterprise Edition,
> and
> will there be any problem if i uninstall it and reinstall the Standard
> edition?
>
> Thanking u in advance Lara
>|||I missed out the link for SQLPing and SQLRecon!
http://www.sqlsecurity.com/DesktopDefault.aspx?tabid=26
John
"John Bell" <jbellnewsposts@.hotmail.com> wrote in message
news:%23nvI0tqZFHA.1404@.TK2MSFTNGP09.phx.gbl...
> Hi
> You should have no problems with un-installing Enterprise Edition and
> re-installing Standard if you are not using any of the additional features
> that it has. You may want to look at
> http://support.microsoft.com/defaul...b;en-us;Q314546 for
> transferring logins and dealing with Orphaned users if you have them. Make
> sure that the new version is service packed and patched to the same level.
> Backing up your database before un-installation will make sure that you
> have a safe copy.
> When you install the new system make sure that the correct protocols are
> listed on the server's server network utilities. Check that you can ping
> the server from your client and that the client also has the correct
> network protocols. You may want to try SQLPing or SQLRecon to see if the
> server is contactable.
> John
>
> "lara" <lara@.l.com> wrote in message
> news:eOx2EApZFHA.1088@.TK2MSFTNGP14.phx.gbl...
>|||Thanks John
"John Bell" <jbellnewsposts@.hotmail.com> wrote in message
news:eNJEsvqZFHA.3572@.TK2MSFTNGP12.phx.gbl...
> I missed out the link for SQLPing and SQLRecon!
> http://www.sqlsecurity.com/DesktopDefault.aspx?tabid=26
> John
> "John Bell" <jbellnewsposts@.hotmail.com> wrote in message
> news:%23nvI0tqZFHA.1404@.TK2MSFTNGP09.phx.gbl...
features
Make
level.
i
Edition,
>
I have a pbm while connecting to the remote SQL server.
Recently we hired one win2003 based Dedicated server and installed SQl
server 2000. I have the sa password and the ip of the server, and when i
connect to this server from my local machine by configuring client n/w
utility, its giving me the error. like SQL server Does not exists ?
What shall i do ? i've disabled the firewall also, but not successful yet.
Also one more problem. The version i've installed is Enterprise Edition, and
will there be any problem if i uninstall it and reinstall the Standard
edition?
Thanking u in advance LaraHi
You should have no problems with un-installing Enterprise Edition and
re-installing Standard if you are not using any of the additional features
that it has. You may want to look at
http://support.microsoft.com/defaul...b;en-us;Q314546 for
transferring logins and dealing with Orphaned users if you have them. Make
sure that the new version is service packed and patched to the same level.
Backing up your database before un-installation will make sure that you have
a safe copy.
When you install the new system make sure that the correct protocols are
listed on the server's server network utilities. Check that you can ping the
server from your client and that the client also has the correct network
protocols. You may want to try SQLPing or SQLRecon to see if the server is
contactable.
John
"lara" <lara@.l.com> wrote in message
news:eOx2EApZFHA.1088@.TK2MSFTNGP14.phx.gbl...
> Hi,
> I have a pbm while connecting to the remote SQL server.
> Recently we hired one win2003 based Dedicated server and installed SQl
> server 2000. I have the sa password and the ip of the server, and when i
> connect to this server from my local machine by configuring client n/w
> utility, its giving me the error. like SQL server Does not exists ?
> What shall i do ? i've disabled the firewall also, but not successful yet.
> Also one more problem. The version i've installed is Enterprise Edition,
> and
> will there be any problem if i uninstall it and reinstall the Standard
> edition?
>
> Thanking u in advance Lara
>|||I missed out the link for SQLPing and SQLRecon!
http://www.sqlsecurity.com/DesktopDefault.aspx?tabid=26
John
"John Bell" <jbellnewsposts@.hotmail.com> wrote in message
news:%23nvI0tqZFHA.1404@.TK2MSFTNGP09.phx.gbl...
> Hi
> You should have no problems with un-installing Enterprise Edition and
> re-installing Standard if you are not using any of the additional features
> that it has. You may want to look at
> http://support.microsoft.com/defaul...b;en-us;Q314546 for
> transferring logins and dealing with Orphaned users if you have them. Make
> sure that the new version is service packed and patched to the same level.
> Backing up your database before un-installation will make sure that you
> have a safe copy.
> When you install the new system make sure that the correct protocols are
> listed on the server's server network utilities. Check that you can ping
> the server from your client and that the client also has the correct
> network protocols. You may want to try SQLPing or SQLRecon to see if the
> server is contactable.
> John
>
> "lara" <lara@.l.com> wrote in message
> news:eOx2EApZFHA.1088@.TK2MSFTNGP14.phx.gbl...
>|||Thanks John
"John Bell" <jbellnewsposts@.hotmail.com> wrote in message
news:eNJEsvqZFHA.3572@.TK2MSFTNGP12.phx.gbl...
> I missed out the link for SQLPing and SQLRecon!
> http://www.sqlsecurity.com/DesktopDefault.aspx?tabid=26
> John
> "John Bell" <jbellnewsposts@.hotmail.com> wrote in message
> news:%23nvI0tqZFHA.1404@.TK2MSFTNGP09.phx.gbl...
features
Make
level.
i
Edition,
>
Monday, February 20, 2012
passing SELECT result to OS
In Windows, I have a folder, lets say 'ABC'. I'd like this folder to be
renamed only a daily basis, based the current datestamp, through T-SQL. So
far, I've come up the following T-SQL stmt:
SELECT RTRIM(LEFT(DATENAME(month, getdate()),3)+DATENAME(day,
getdate())+DATENAME(year, getdate()))
...How would I be able to implement the result of the above stament (in the
case, Feb232006) to be the new folder name, i.e., take the result of the SQL
select stmt. and pass it to the OS to rename a folder?
Thanks.DECLARE @.cmd VARCHAR(255);
SET @.cmd = 'ren "d:\abc\" "foo"';
EXEC master..xp_cmdshell @.cmd, NO_OUTPUT;
"Rob" <Rob@.discussions.microsoft.com> wrote in message
news:D2B570A3-A31A-4C80-A5E2-44ABD38E52BE@.microsoft.com...
> In Windows, I have a folder, lets say 'ABC'. I'd like this folder to be
> renamed only a daily basis, based the current datestamp, through T-SQL. So
> far, I've come up the following T-SQL stmt:
> SELECT RTRIM(LEFT(DATENAME(month, getdate()),3)+DATENAME(day,
> getdate())+DATENAME(year, getdate()))
> ...How would I be able to implement the result of the above stament (in
> the
> case, Feb232006) to be the new folder name, i.e., take the result of the
> SQL
> select stmt. and pass it to the OS to rename a folder?
> Thanks.|||"Rob" <Rob@.discussions.microsoft.com> wrote in message
news:D2B570A3-A31A-4C80-A5E2-44ABD38E52BE@.microsoft.com...
> In Windows, I have a folder, lets say 'ABC'. I'd like this folder to be
> renamed only a daily basis, based the current datestamp, through T-SQL. So
> far, I've come up the following T-SQL stmt:
> SELECT RTRIM(LEFT(DATENAME(month, getdate()),3)+DATENAME(day,
> getdate())+DATENAME(year, getdate()))
> ...How would I be able to implement the result of the above stament (in
> the
> case, Feb232006) to be the new folder name, i.e., take the result of the
> SQL
> select stmt. and pass it to the OS to rename a folder?
> Thanks.
Lookup xp_cmdshell in Books Online. Why do it in SQL though?
Your naming convention for folders looks very inconvenient. The user will
see the months sorted alphabetically in Explorer instead of chronologically.
The years will be mixed up too! Better to do:
\2006_02_23
\2006_02_24
\... etc
David Portas, SQL Server MVP
Whenever possible please post enough code to reproduce your problem.
Including CREATE TABLE and INSERT statements usually helps.
State what version of SQL Server you are using and specify the content
of any error messages.
SQL Server Books Online:
http://msdn2.microsoft.com/library/ms130214(en-US,SQL.90).aspx
--|||It's okay... I figured it out myself by using the following code:
declare @.date varchar(10)
declare @.cmd varchar(250)
set @.date = RTRIM(LEFT(DATENAME(month, getdate()),3)+DATENAME(day,
getdate())+DATENAME(year, getdate()))
Print @.date
set @.cmd = 'REN X:\ABC ' + @.date
Print @.cmd
"Rob" wrote:
> In Windows, I have a folder, lets say 'ABC'. I'd like this folder to be
> renamed only a daily basis, based the current datestamp, through T-SQL. So
> far, I've come up the following T-SQL stmt:
> SELECT RTRIM(LEFT(DATENAME(month, getdate()),3)+DATENAME(day,
> getdate())+DATENAME(year, getdate()))
> ...How would I be able to implement the result of the above stament (in th
e
> case, Feb232006) to be the new folder name, i.e., take the result of the S
QL
> select stmt. and pass it to the OS to rename a folder?
> Thanks.
renamed only a daily basis, based the current datestamp, through T-SQL. So
far, I've come up the following T-SQL stmt:
SELECT RTRIM(LEFT(DATENAME(month, getdate()),3)+DATENAME(day,
getdate())+DATENAME(year, getdate()))
...How would I be able to implement the result of the above stament (in the
case, Feb232006) to be the new folder name, i.e., take the result of the SQL
select stmt. and pass it to the OS to rename a folder?
Thanks.DECLARE @.cmd VARCHAR(255);
SET @.cmd = 'ren "d:\abc\" "foo"';
EXEC master..xp_cmdshell @.cmd, NO_OUTPUT;
"Rob" <Rob@.discussions.microsoft.com> wrote in message
news:D2B570A3-A31A-4C80-A5E2-44ABD38E52BE@.microsoft.com...
> In Windows, I have a folder, lets say 'ABC'. I'd like this folder to be
> renamed only a daily basis, based the current datestamp, through T-SQL. So
> far, I've come up the following T-SQL stmt:
> SELECT RTRIM(LEFT(DATENAME(month, getdate()),3)+DATENAME(day,
> getdate())+DATENAME(year, getdate()))
> ...How would I be able to implement the result of the above stament (in
> the
> case, Feb232006) to be the new folder name, i.e., take the result of the
> SQL
> select stmt. and pass it to the OS to rename a folder?
> Thanks.|||"Rob" <Rob@.discussions.microsoft.com> wrote in message
news:D2B570A3-A31A-4C80-A5E2-44ABD38E52BE@.microsoft.com...
> In Windows, I have a folder, lets say 'ABC'. I'd like this folder to be
> renamed only a daily basis, based the current datestamp, through T-SQL. So
> far, I've come up the following T-SQL stmt:
> SELECT RTRIM(LEFT(DATENAME(month, getdate()),3)+DATENAME(day,
> getdate())+DATENAME(year, getdate()))
> ...How would I be able to implement the result of the above stament (in
> the
> case, Feb232006) to be the new folder name, i.e., take the result of the
> SQL
> select stmt. and pass it to the OS to rename a folder?
> Thanks.
Lookup xp_cmdshell in Books Online. Why do it in SQL though?
Your naming convention for folders looks very inconvenient. The user will
see the months sorted alphabetically in Explorer instead of chronologically.
The years will be mixed up too! Better to do:
\2006_02_23
\2006_02_24
\... etc
David Portas, SQL Server MVP
Whenever possible please post enough code to reproduce your problem.
Including CREATE TABLE and INSERT statements usually helps.
State what version of SQL Server you are using and specify the content
of any error messages.
SQL Server Books Online:
http://msdn2.microsoft.com/library/ms130214(en-US,SQL.90).aspx
--|||It's okay... I figured it out myself by using the following code:
declare @.date varchar(10)
declare @.cmd varchar(250)
set @.date = RTRIM(LEFT(DATENAME(month, getdate()),3)+DATENAME(day,
getdate())+DATENAME(year, getdate()))
Print @.date
set @.cmd = 'REN X:\ABC ' + @.date
Print @.cmd
"Rob" wrote:
> In Windows, I have a folder, lets say 'ABC'. I'd like this folder to be
> renamed only a daily basis, based the current datestamp, through T-SQL. So
> far, I've come up the following T-SQL stmt:
> SELECT RTRIM(LEFT(DATENAME(month, getdate()),3)+DATENAME(day,
> getdate())+DATENAME(year, getdate()))
> ...How would I be able to implement the result of the above stament (in th
e
> case, Feb232006) to be the new folder name, i.e., take the result of the S
QL
> select stmt. and pass it to the OS to rename a folder?
> Thanks.
Subscribe to:
Posts (Atom)