Disabling AutoRendering for Reports with Default Parameters

I have a report with default parameters. Every time the report is selected,
it automatically renders the report using the defaults. Is there any way to
disable the AutoRendering feature so my users can choose to override the
report's defaults and then render the report manually?
--
Jay P. Meredith
Senior Software Engineer
Columbia Helicopters, Inc.
PO Box 3500
Portland, OR 97208Just a stab, but maybe worth trying... What if you add a hidden parameter
which has no default value, and is not used... That might prevent
auto-render, and force the user to select the view report button... ( I
don't know what potential bad side effects might occur tho...)
--
Wayne Snyder, MCDBA, SQL Server MVP
Mariner, Charlotte, NC
www.mariner-usa.com
(Please respond only to the newsgroups.)
I support the Professional Association of SQL Server (PASS) and it's
community of SQL Server professionals.
www.sqlpass.org
"Jay Meredith" <JayMeredith@.discussions.microsoft.com> wrote in message
news:5E0D389A-8EE3-417B-A658-8DFCBD01D483@.microsoft.com...
>I have a report with default parameters. Every time the report is
>selected,
> it automatically renders the report using the defaults. Is there any way
> to
> disable the AutoRendering feature so my users can choose to override the
> report's defaults and then render the report manually?
> --
> Jay P. Meredith
> Senior Software Engineer
> Columbia Helicopters, Inc.
> PO Box 3500
> Portland, OR 97208|||Wayne,
A hidden parameter with no default value will cause the report not to render
at all. After all, if it has no default, it has to be told what its value
is. And if the user can't see it to choose a value, then the report will
just sit there, waiting for input.
The only way I've found against AutoRender when the report is first open is
to leave one of my parameters with no default, forcing the user to make a
choice on it.
BLARGH... It would be nice if RS was old enough that someone else had all
the answers and we didn't have to be the ones to find out the answers the
hard way. @.=/
Catadmin
--
MCDBA, MCSA
Random Thoughts: If a person is Microsoft Certified, does that mean that
Microsoft pays the bills for the funny white jackets that tie in the back?
@.=)
"Wayne Snyder" wrote:
> Just a stab, but maybe worth trying... What if you add a hidden parameter
> which has no default value, and is not used... That might prevent
> auto-render, and force the user to select the view report button... ( I
> don't know what potential bad side effects might occur tho...)
> --
> Wayne Snyder, MCDBA, SQL Server MVP
> Mariner, Charlotte, NC
> www.mariner-usa.com
> (Please respond only to the newsgroups.)
> I support the Professional Association of SQL Server (PASS) and it's
> community of SQL Server professionals.
> www.sqlpass.org
> "Jay Meredith" <JayMeredith@.discussions.microsoft.com> wrote in message
> news:5E0D389A-8EE3-417B-A658-8DFCBD01D483@.microsoft.com...
> >I have a report with default parameters. Every time the report is
> >selected,
> > it automatically renders the report using the defaults. Is there any way
> > to
> > disable the AutoRendering feature so my users can choose to override the
> > report's defaults and then render the report manually?
> > --
> > Jay P. Meredith
> > Senior Software Engineer
> > Columbia Helicopters, Inc.
> > PO Box 3500
> > Portland, OR 97208
>
>|||Leaving one or more unhidden parameters without defaults seems to be the best
compromise. In defaulting all parameters, I was trying to save the user a
few keystrokes. Thanks.
--
Jay P. Meredith
Senior Software Engineer
Columbia Helicopters, Inc.
PO Box 3500
Portland, OR 97208
"Catadmin" wrote:
> Wayne,
> A hidden parameter with no default value will cause the report not to render
> at all. After all, if it has no default, it has to be told what its value
> is. And if the user can't see it to choose a value, then the report will
> just sit there, waiting for input.
> The only way I've found against AutoRender when the report is first open is
> to leave one of my parameters with no default, forcing the user to make a
> choice on it.
> BLARGH... It would be nice if RS was old enough that someone else had all
> the answers and we didn't have to be the ones to find out the answers the
> hard way. @.=/
> Catadmin
> --
> MCDBA, MCSA
> Random Thoughts: If a person is Microsoft Certified, does that mean that
> Microsoft pays the bills for the funny white jackets that tie in the back?
> @.=)
>
> "Wayne Snyder" wrote:
> > Just a stab, but maybe worth trying... What if you add a hidden parameter
> > which has no default value, and is not used... That might prevent
> > auto-render, and force the user to select the view report button... ( I
> > don't know what potential bad side effects might occur tho...)
> >
> > --
> > Wayne Snyder, MCDBA, SQL Server MVP
> > Mariner, Charlotte, NC
> > www.mariner-usa.com
> > (Please respond only to the newsgroups.)
> >
> > I support the Professional Association of SQL Server (PASS) and it's
> > community of SQL Server professionals.
> > www.sqlpass.org
> >
> > "Jay Meredith" <JayMeredith@.discussions.microsoft.com> wrote in message
> > news:5E0D389A-8EE3-417B-A658-8DFCBD01D483@.microsoft.com...
> > >I have a report with default parameters. Every time the report is
> > >selected,
> > > it automatically renders the report using the defaults. Is there any way
> > > to
> > > disable the AutoRendering feature so my users can choose to override the
> > > report's defaults and then render the report manually?
> > > --
> > > Jay P. Meredith
> > > Senior Software Engineer
> > > Columbia Helicopters, Inc.
> > > PO Box 3500
> > > Portland, OR 97208
> >
> >
> >|||Always glad to be of assistance. @.=)
Catadmin
"Jay Meredith" wrote:
> Leaving one or more unhidden parameters without defaults seems to be the best
> compromise. In defaulting all parameters, I was trying to save the user a
> few keystrokes. Thanks.
> --
> Jay P. Meredith
> Senior Software Engineer
> Columbia Helicopters, Inc.
> PO Box 3500
> Portland, OR 97208
>
> "Catadmin" wrote:
> > Wayne,
> >
> > A hidden parameter with no default value will cause the report not to render
> > at all. After all, if it has no default, it has to be told what its value
> > is. And if the user can't see it to choose a value, then the report will
> > just sit there, waiting for input.
> >
> > The only way I've found against AutoRender when the report is first open is
> > to leave one of my parameters with no default, forcing the user to make a
> > choice on it.
> >
> > BLARGH... It would be nice if RS was old enough that someone else had all
> > the answers and we didn't have to be the ones to find out the answers the
> > hard way. @.=/
> >
> > Catadmin
> > --
> > MCDBA, MCSA
> > Random Thoughts: If a person is Microsoft Certified, does that mean that
> > Microsoft pays the bills for the funny white jackets that tie in the back?
> > @.=)
> >
> >
> > "Wayne Snyder" wrote:
> >
> > > Just a stab, but maybe worth trying... What if you add a hidden parameter
> > > which has no default value, and is not used... That might prevent
> > > auto-render, and force the user to select the view report button... ( I
> > > don't know what potential bad side effects might occur tho...)
> > >
> > > --
> > > Wayne Snyder, MCDBA, SQL Server MVP
> > > Mariner, Charlotte, NC
> > > www.mariner-usa.com
> > > (Please respond only to the newsgroups.)
> > >
> > > I support the Professional Association of SQL Server (PASS) and it's
> > > community of SQL Server professionals.
> > > www.sqlpass.org
> > >
> > > "Jay Meredith" <JayMeredith@.discussions.microsoft.com> wrote in message
> > > news:5E0D389A-8EE3-417B-A658-8DFCBD01D483@.microsoft.com...
> > > >I have a report with default parameters. Every time the report is
> > > >selected,
> > > > it automatically renders the report using the defaults. Is there any way
> > > > to
> > > > disable the AutoRendering feature so my users can choose to override the
> > > > report's defaults and then render the report manually?
> > > > --
> > > > Jay P. Meredith
> > > > Senior Software Engineer
> > > > Columbia Helicopters, Inc.
> > > > PO Box 3500
> > > > Portland, OR 97208
> > >
> > >
> > >

Disable constraint creation for subscriber

Hello,

It seems we have a table that is on merge replication the table by default doesn't have a PK on it. This table only has about 50 rows of data, somewhere during the initialization process it's trying to create a PK by default on the client end. My assumption is during the creation of the snapshot a script is being generated that we do not want. How can we prevent them from happening as it's creating a PK violation.

The schema script 'if object_id(N'[dbo].[checklistimported]') is not null exec('ALTER TABLE [dbo].[checklistimported] ADD CONSTRAINT
PK_listimported PRIMARY KEY CLUSTERED
(
projectid,
chklstid,
unit,
lot
) WITH( STATISTICS_NORECOMPUTE = OFF, IGNORE_DUP_KEY = OFF, ALLOW_ROW_LOCKS = ON, ALLOW_PAGE_LOCKS = ON) ON [PRIMARY]

')' could not be propagated to the subscriber due to an error in creating index. A possible cause of this error is one or more join filters has the join_unique_key property se

server SQL2k5 SP1

client SQL Express

Actually the PK should have existed at the publisher side. If it does not exist at the publisher side, it will not be created at the subscriber side.

Are the two servers (publisher and subscriber) with the same case sensitivity? I am suspecting that's the problem.

disable automatic execution and rendering

I use asp.net page to view the reports. Some of my reports take parameters
and I set them default to '%' as while cards.
When a report link is clicked, the report is executed and rendered when the
new page is open. Some of them returns really quite some records so it takes
a while to have the page rendered.
Is there a setting somewhere that the reports are not executed and rendered
when the hosting page is open and the process will start only when the "View
Report" button is clicked?
Thank you.You need at least one parameter to not have a default. Otherwise it renders
automatically. I would prefer this behaviour to be different. I haven't
checked 2005 to see if it has changed but this is the way it works in 2000.
Bruce Loehle-Conger
MVP SQL Server Reporting Services
"ZWeng" <ZWeng@.discussions.microsoft.com> wrote in message
news:32F0A618-C751-479F-9FE1-7CF542E71A35@.microsoft.com...
>I use asp.net page to view the reports. Some of my reports take parameters
> and I set them default to '%' as while cards.
> When a report link is clicked, the report is executed and rendered when
> the
> new page is open. Some of them returns really quite some records so it
> takes
> a while to have the page rendered.
> Is there a setting somewhere that the reports are not executed and
> rendered
> when the hosting page is open and the process will start only when the
> "View
> Report" button is clicked?
> Thank you.
>|||It still works the same way in RS 2005... It would be nice to have a
No-Autorender flag...
--
Wayne Snyder MCDBA, SQL Server MVP
Mariner, Charlotte, NC
I support the Professional Association for SQL Server ( PASS) and it''s
community of SQL Professionals.
"Bruce L-C [MVP]" wrote:
> You need at least one parameter to not have a default. Otherwise it renders
> automatically. I would prefer this behaviour to be different. I haven't
> checked 2005 to see if it has changed but this is the way it works in 2000.
>
> --
> Bruce Loehle-Conger
> MVP SQL Server Reporting Services
> "ZWeng" <ZWeng@.discussions.microsoft.com> wrote in message
> news:32F0A618-C751-479F-9FE1-7CF542E71A35@.microsoft.com...
> >I use asp.net page to view the reports. Some of my reports take parameters
> > and I set them default to '%' as while cards.
> >
> > When a report link is clicked, the report is executed and rendered when
> > the
> > new page is open. Some of them returns really quite some records so it
> > takes
> > a while to have the page rendered.
> >
> > Is there a setting somewhere that the reports are not executed and
> > rendered
> > when the hosting page is open and the process will start only when the
> > "View
> > Report" button is clicked?
> >
> > Thank you.
> >
> >
>
>