This is a multi-part message in MIME format.
--=_NextPart_000_0006_01C75F65.85B0F190
Content-Type: text/plain;
charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
Is it possible to base an expression on whether a group is expanded or = not?
I want to show totals in the header, unless the group is expanded. In = that case, I want to show totals in the footer.
This would have to be dynamic, but i don't know if you have that kind of = access to the report objects when the report is being displayed. = Thanks.
J
--=_NextPart_000_0006_01C75F65.85B0F190
Content-Type: text/html;
charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
&
Is it possible to base an expression on = whether a group is expanded or not?
I want to show totals in the header, = unless the group is expanded. In that case, I want to show totals in the footer.
This would have to be dynamic, but i = don't know if you have that kind of access to the report objects when the report is = being displayed. Thanks.
J
--=_NextPart_000_0006_01C75F65.85B0F190--On Mar 5, 9:33 pm, <rlrc...@.newsgroups.nospam> wrote:
> Is it possible to base an expression on whether a group is expanded or not?
> I want to show totals in the header, unless the group is expanded. In that case, I want to show totals in the footer.
> This would have to be dynamic, but i don't know if you have that kind of access to the report objects when the report is being displayed. Thanks.
> J
As far as I know, this functionality does not exist.
Regards,
Enrique Martinez
Sr. SQL Server Developersql
Showing posts with label expanded. Show all posts
Showing posts with label expanded. Show all posts
Thursday, March 22, 2012
Friday, March 9, 2012
detach 6.5 compatible database in studio - HOW?
I've got two databases showing in the studio tree, but they are marked 6.5 compatible and cannot be expanded. Worse, there is no way (apparently) in the menu of either database to remove, delete or detach them.
How can I get these out of the system?
Thanks in advance.
randyv
What about using the TSQL statement for dropping / detaching the databases ? (DROP DATABASE / sp_detach)HTH, Jens K. Suessmeyer.
http://www.sqlserver2005.de
No, that doesn't work because it is grayed out... It finally dawned on me that since I could not take any action directly on the database due to compatibility problems, but that the database was from 2000, there was no reason the level could not be increased.
To make sure I had no problem with the application, this is what I did. I backed up the database on the 2000 server, then restored it as a different database. Then I changed the compatibility level on that restored database to 80.
Next I backed that databased up and copied the .bak file to the other server running 2005.
Then I restored that .bak file as the existing 6.5 level database with a restore over existing database flag turned on.
Presto ! Problem solved. It is taking the long way around the problem, but there is no other option open, apparently.
|||Try to run this transact sql script against your database:
USE databaseName
GO
EXECUTE sp_dbcmptlevel databaseName , 90
GO
EXEC sp_updatestats
GO
detach 6.5 compatible database in studio - HOW?
I've got two databases showing in the studio tree, but they are marked 6.5 compatible and cannot be expanded. Worse, there is no way (apparently) in the menu of either database to remove, delete or detach them.
How can I get these out of the system?
Thanks in advance.
randyv
What about using the TSQL statement for dropping / detaching the databases ? (DROP DATABASE / sp_detach)HTH, Jens K. Suessmeyer.
http://www.sqlserver2005.de
No, that doesn't work because it is grayed out... It finally dawned on me that since I could not take any action directly on the database due to compatibility problems, but that the database was from 2000, there was no reason the level could not be increased.
To make sure I had no problem with the application, this is what I did. I backed up the database on the 2000 server, then restored it as a different database. Then I changed the compatibility level on that restored database to 80.
Next I backed that databased up and copied the .bak file to the other server running 2005.
Then I restored that .bak file as the existing 6.5 level database with a restore over existing database flag turned on.
Presto ! Problem solved. It is taking the long way around the problem, but there is no other option open, apparently.
|||Try to run this transact sql script against your database:
USE databaseName
GO
EXECUTE sp_dbcmptlevel databaseName , 90
GO
EXEC sp_updatestats
GO
detach 6.5 compatible database in studio - HOW?
I've got two databases showing in the studio tree, but they are marked 6.5 compatible and cannot be expanded. Worse, there is no way (apparently) in the menu of either database to remove, delete or detach them.
How can I get these out of the system?
Thanks in advance.
randyv
What about using the TSQL statement for dropping / detaching the databases ? (DROP DATABASE / sp_detach)HTH, Jens K. Suessmeyer.
http://www.sqlserver2005.de
No, that doesn't work because it is grayed out... It finally dawned on me that since I could not take any action directly on the database due to compatibility problems, but that the database was from 2000, there was no reason the level could not be increased.
To make sure I had no problem with the application, this is what I did. I backed up the database on the 2000 server, then restored it as a different database. Then I changed the compatibility level on that restored database to 80.
Next I backed that databased up and copied the .bak file to the other server running 2005.
Then I restored that .bak file as the existing 6.5 level database with a restore over existing database flag turned on.
Presto ! Problem solved. It is taking the long way around the problem, but there is no other option open, apparently.
|||Try to run this transact sql script against your database:
USE databaseName
GO
EXECUTE sp_dbcmptlevel databaseName , 90
GO
EXEC sp_updatestats
GO
Subscribe to:
Posts (Atom)