Report Designer: preview goes into infinite loop

Hello,
Situation:
- a report with cascading parameters [A], [B], [C]
- first parameter [A] loaded via non-queried values
- second parameter [B] loaded via stored procedure, taking [A] and a
constant as input (via dataset dsB)
- third parameter [C] loaded via the same stored procedure, taking [A] and
[B] as input (via dataset dsC)
When I preview this report:
- initial view ok
- modify [A] -> [B] changes accordingly
- modify [B] -> the designer starts flickering and goes into a never ending
loop.
The deployed report works just fine and as expected.
Bug ? Any work arounds ?
Thanks for any input!
TomSounds like a bug. There is another bug I have found with the preview tab
and cascading parameters. It only cascades once. I.e. if you go back a
second time and change A it does not change B. Again, deploy works fine. I
have access to the the internal bug reporting tool and when I report the
previous but I'll do this one too. I am not aware of any workaround. At
least it works in deployed mode.
--
Bruce Loehle-Conger
MVP SQL Server Reporting Services
"Tom VdP" <unick@.hot_mail_.c-o-m> wrote in message
news:1FBF14D5-28E3-4B76-93BF-47F292BC33FE@.microsoft.com...
> Hello,
> Situation:
> - a report with cascading parameters [A], [B], [C]
> - first parameter [A] loaded via non-queried values
> - second parameter [B] loaded via stored procedure, taking [A] and a
> constant as input (via dataset dsB)
> - third parameter [C] loaded via the same stored procedure, taking [A] and
> [B] as input (via dataset dsC)
> When I preview this report:
> - initial view ok
> - modify [A] -> [B] changes accordingly
> - modify [B] -> the designer starts flickering and goes into a never
ending
> loop.
> The deployed report works just fine and as expected.
> Bug ? Any work arounds ?
> Thanks for any input!
> Tom|||Thanks for reporting it.
It is annoying as the first parameter in our reports is the choice of
language. Depending on the selection the contents of the other dropdown
boxes is changed.
So we have cascading parameters in every report.
But we can use the deployed reports luckily.
Regards,
Tom
"Bruce L-C [MVP]" wrote:
> Sounds like a bug. There is another bug I have found with the preview tab
> and cascading parameters. It only cascades once. I.e. if you go back a
> second time and change A it does not change B. Again, deploy works fine. I
> have access to the the internal bug reporting tool and when I report the
> previous but I'll do this one too. I am not aware of any workaround. At
> least it works in deployed mode.
> --
> Bruce Loehle-Conger
> MVP SQL Server Reporting Services
>
> "Tom VdP" <unick@.hot_mail_.c-o-m> wrote in message
> news:1FBF14D5-28E3-4B76-93BF-47F292BC33FE@.microsoft.com...
> >
> > Hello,
> >
> > Situation:
> > - a report with cascading parameters [A], [B], [C]
> > - first parameter [A] loaded via non-queried values
> > - second parameter [B] loaded via stored procedure, taking [A] and a
> > constant as input (via dataset dsB)
> > - third parameter [C] loaded via the same stored procedure, taking [A] and
> > [B] as input (via dataset dsC)
> >
> > When I preview this report:
> > - initial view ok
> > - modify [A] -> [B] changes accordingly
> > - modify [B] -> the designer starts flickering and goes into a never
> ending
> > loop.
> >
> > The deployed report works just fine and as expected.
> >
> > Bug ? Any work arounds ?
> >
> > Thanks for any input!
> > Tom
>
>|||I am not using cascading parameters but I have experieced a similiar problems
with the Report Designer preview (loops) and I sometimes get a Processing
Error 'Specified Cast in not Valid' , If I remove the Page Header OR Footer I
do not get the error, OR if there is labels only (no ReportItems! or Globals!
in the header/footer) it works.
There are no problems when the report is deployed.
"Tom VdP" wrote:
> Thanks for reporting it.
> It is annoying as the first parameter in our reports is the choice of
> language. Depending on the selection the contents of the other dropdown
> boxes is changed.
> So we have cascading parameters in every report.
> But we can use the deployed reports luckily.
> Regards,
> Tom
>
> "Bruce L-C [MVP]" wrote:
> > Sounds like a bug. There is another bug I have found with the preview tab
> > and cascading parameters. It only cascades once. I.e. if you go back a
> > second time and change A it does not change B. Again, deploy works fine. I
> > have access to the the internal bug reporting tool and when I report the
> > previous but I'll do this one too. I am not aware of any workaround. At
> > least it works in deployed mode.
> > --
> > Bruce Loehle-Conger
> > MVP SQL Server Reporting Services
> >
> >
> > "Tom VdP" <unick@.hot_mail_.c-o-m> wrote in message
> > news:1FBF14D5-28E3-4B76-93BF-47F292BC33FE@.microsoft.com...
> > >
> > > Hello,
> > >
> > > Situation:
> > > - a report with cascading parameters [A], [B], [C]
> > > - first parameter [A] loaded via non-queried values
> > > - second parameter [B] loaded via stored procedure, taking [A] and a
> > > constant as input (via dataset dsB)
> > > - third parameter [C] loaded via the same stored procedure, taking [A] and
> > > [B] as input (via dataset dsC)
> > >
> > > When I preview this report:
> > > - initial view ok
> > > - modify [A] -> [B] changes accordingly
> > > - modify [B] -> the designer starts flickering and goes into a never
> > ending
> > > loop.
> > >
> > > The deployed report works just fine and as expected.
> > >
> > > Bug ? Any work arounds ?
> > >
> > > Thanks for any input!
> > > Tom
> >
> >
> >

Report Designer crashes when accessing Access DB via ODBC

Hi:
I am trying to build a report off of a stand alone MS Access 2000 database. I can create the Data Source using the "Driver do Microsoft Access" driver, version 4.00.6019.00.
When I go to create the query to create the Dataset, I right click to add a table, I can see the table list and check the table I want to use. It is at this point the Visual Studio crashes, closes and send off the error report to Microsoft.
What's up? Why is this happening? I can write reports to my heart's content using an IBM ODBC driver against our DB2 database on an AS/400. One would think that writing reports using all MS products this should go very smooth.
Thanks in advance.
Bruce.Did you try the "Microsoft Jet 4.0 OLE DB Provider" which is designed to
work with Access?
--
This posting is provided "AS IS" with no warranties, and confers no rights.
"bwschiek@.hotmail.com" <bwschiekhotmailcom@.discussions.microsoft.com> wrote
in message news:EE8C1C06-2779-4069-9004-0E6DF55969CE@.microsoft.com...
> Hi:
> I am trying to build a report off of a stand alone MS Access 2000
database. I can create the Data Source using the "Driver do Microsoft
Access" driver, version 4.00.6019.00.
> When I go to create the query to create the Dataset, I right click to add
a table, I can see the table list and check the table I want to use. It is
at this point the Visual Studio crashes, closes and send off the error
report to Microsoft.
> What's up? Why is this happening? I can write reports to my heart's
content using an IBM ODBC driver against our DB2 database on an AS/400. One
would think that writing reports using all MS products this should go very
smooth.
> Thanks in advance.
> Bruce.|||Hi Robert:
Thanks. That did the trick.
I had been using the ODBC connection that caused VS to crash for the last year with Crystal Reports with no issues. Curious...
Thanks again.
Bruce.
"Robert Bruckner [MSFT]" wrote:
> Did you try the "Microsoft Jet 4.0 OLE DB Provider" which is designed to
> work with Access?
> --
> This posting is provided "AS IS" with no warranties, and confers no rights.
>
> "bwschiek@.hotmail.com" <bwschiekhotmailcom@.discussions.microsoft.com> wrote
> in message news:EE8C1C06-2779-4069-9004-0E6DF55969CE@.microsoft.com...
> > Hi:
> >
> > I am trying to build a report off of a stand alone MS Access 2000
> database. I can create the Data Source using the "Driver do Microsoft
> Access" driver, version 4.00.6019.00.
> >
> > When I go to create the query to create the Dataset, I right click to add
> a table, I can see the table list and check the table I want to use. It is
> at this point the Visual Studio crashes, closes and send off the error
> report to Microsoft.
> >
> > What's up? Why is this happening? I can write reports to my heart's
> content using an IBM ODBC driver against our DB2 database on an AS/400. One
> would think that writing reports using all MS products this should go very
> smooth.
> >
> > Thanks in advance.
> >
> > Bruce.
>
>

report compress

Hello,
I just wonder if there is anyway to compress the report before sending it to
customer via email?
Thanks
HoomanOn Jun 27, 1:37 pm, "Hooman" <Hoo...@.ebatts.com> wrote:
> Hello,
> I just wonder if there is anyway to compress the report before sending it to
> customer via email?
> Thanks
> Hooman
You could try looking for third party compression tools (WinZip, etc).
Also, check out this link for a programmatic option.
http://groups.google.com/group/microsoft.public.dotnet.languages.vb/browse_thread/thread/22dc93e52e4817ed/3b360d41d005f3c3?lnk=st&q=programmatically+compress+files&rnum=3#3b360d41d005f3c3
Hope this helps.
Regards,
Enrique Martinez
Sr. Software Consultant

Report Column Headers from Database table

Please is it possible to get the reports column names from database table via stored proc or a select query.

Because reports needs to be localized between spanish and english users, so if a spanish user is logged into the system, it must bring all spanish column names from DB table and show in the headers, same with english users.

Thank you very much for the information.

I am using SQL 2K Reporting services.

Are the column names from a different dataset than the rest of the data in the report? If so, you have the following options:

1. Modify the query to return them in the same dataset (since you can't use two datasets in the same table).

2. Modify the report to include two tables, one only has the table header for the column names, the other (without header) displays the detail data, and align them appropriately.

3. Use subreport embedded in the table to display the detail data.

sql

Report Builder button doesn't appear....

Users must have permission to the Execute Report Definitions task (normally obtained via the System Users role) for the Report Builder button to be displayed.
--Original Message--
From: Jay@.discussions.microsoft.com
Posted At: Friday, October 21, 2005 4:01 PM
Posted To: microsoft.public.sqlserver.reportingsvcs
Conversation: Report Builder button doesn't appear...
Subject: RE: Report Builder button doesn't appear...
I have run into a similar problem on my machine. The Report Builder button
never appears in my report manager home page.
I'm using Windows 2000 workstation with SQL Server 2005 (September)
Jay
"Allan" wrote:
> Hi,
> I have the latest CTP installed. Users do not see the report builder button.
> Only members of the local admin group seem to have it displayed. Can anyone
> steer me in the right direction'
>
> AllanHow do I do this. Please explain step-by-step. This is a third explanation
I have run across. Please see text below that I posted elsewhere:
Report Builder button does not show when an upgrade to Reporting Services
2005 is completed. If a fresh install is done then no problem. I need to do
an upgrade for an existing Reports Server 2000 and want user to have the
Report Builder button. Some docuementation said to set
EnableReportDesignClientDownload to true, but did not say how to do this.
Another document said Enable Report Design Client Button is set to True in
RSWebApplication.config by default. However, this also did not show how to do
this. I need clear and exact step-by-step instructions.
"Bob Meyers MSFT" wrote:
> Users must have permission to the Execute Report Definitions task (normally obtained via the System Users role) for the Report Builder button to be displayed.
>
> --Original Message--
> From: Jay@.discussions.microsoft.com
> Posted At: Friday, October 21, 2005 4:01 PM
> Posted To: microsoft.public.sqlserver.reportingsvcs
> Conversation: Report Builder button doesn't appear...
> Subject: RE: Report Builder button doesn't appear...
>
> I have run into a similar problem on my machine. The Report Builder button
> never appears in my report manager home page.
> I'm using Windows 2000 workstation with SQL Server 2005 (September)
> Jay
> "Allan" wrote:
> > Hi,
> > I have the latest CTP installed. Users do not see the report builder button.
> > Only members of the local admin group seem to have it displayed. Can anyone
> > steer me in the right direction'
> >
> > Allan
>|||I would also appreciate some help on this. The only time I see the
button is when I'm logged onto the machine that's hosting RS.
Users that have all possible roles assigned do not see the button on
the web site.
How can I make the button visible?

Repopulate Catalog radio button grayed out

I hope someone can help me with this. I know how to start a full-text
population in t-sql. However, I would like to be able to start it via SSMS.
I right click on the catalog and choose properties. All options are
available such as optimize, rebuild, however, repopulate is grayed out.
Any advice?
Thanks.
Has the initial population completed yet? Can you try it by right clicking
on individual full-text indexed tables and selecting Full-text index and
running a full-population?
http://www.zetainteractive.com - Shift Happens!
Looking for a SQL Server replication book?
http://www.nwsu.com/0974973602.html
Looking for a FAQ on Indexing Services/SQL FTS
http://www.indexserverfaq.com
"Aaron" <Aaron@.discussions.microsoft.com> wrote in message
news:8DE20EA0-1A78-4D12-B94B-3C87B4BDC84F@.microsoft.com...
>I hope someone can help me with this. I know how to start a full-text
> population in t-sql. However, I would like to be able to start it via
> SSMS.
> I right click on the catalog and choose properties. All options are
> available such as optimize, rebuild, however, repopulate is grayed out.
> Any advice?
> Thanks.