Showing posts with label number. Show all posts
Showing posts with label number. Show all posts

Wednesday, March 28, 2012

Hide Certain Parameters Dynamically

We have a number of reports which are used by both employees and
administrators with multiple parameters. In many of these reports we have
some parameters unique to the employees which we would like to automatically
set through URL access for our employees and either hide or set them as
read-only so an employee cannot view someone else's data. However, we want
to allow the administrators to change these values so they can view data from
any employee.
So, is there any way to dynamically hide a single parameter while still
showing the remaining ones, or to dynamically make a single parameter
read-only without creating a custom front end? I don't need to know how to
pass default values, just how to programmatically change what parameters are
hidden / read-only.
Thanks in advance.
DavidDavid,
It isn't possible to hide a parameter or make it readonly. A possible
solution for this problem is to create two new reports. One for the employees
and one for the administartors. Both reports get the proper parameters which
they may change. In both reports you include an subreport, the original one
with all parameters. Now you can link the parameters from the report to the
subreport. In teh case for the employees this meens that some parameters of
your original report will have an fixed value.
This solution will also prevent employees from 'trying' out the parameters
with URL Access.
Jan Pieter Posthuma
"David Siebert" wrote:
> We have a number of reports which are used by both employees and
> administrators with multiple parameters. In many of these reports we have
> some parameters unique to the employees which we would like to automatically
> set through URL access for our employees and either hide or set them as
> read-only so an employee cannot view someone else's data. However, we want
> to allow the administrators to change these values so they can view data from
> any employee.
> So, is there any way to dynamically hide a single parameter while still
> showing the remaining ones, or to dynamically make a single parameter
> read-only without creating a custom front end? I don't need to know how to
> pass default values, just how to programmatically change what parameters are
> hidden / read-only.
> Thanks in advance.
> David|||Thanks for the reply, I think I may have found a way that will work for our
needs using linked reports. I created a linked report to the original, and
hid any parameters that the employee does not need to change. It solves the
problem of having to maintain and edit 2 reports when changes are made, and
appears to have solved my issue with being able to change parameter settings
for the 2 separate versions.
"Jan Pieter Posthuma" wrote:
> David,
> It isn't possible to hide a parameter or make it readonly. A possible
> solution for this problem is to create two new reports. One for the employees
> and one for the administartors. Both reports get the proper parameters which
> they may change. In both reports you include an subreport, the original one
> with all parameters. Now you can link the parameters from the report to the
> subreport. In teh case for the employees this meens that some parameters of
> your original report will have an fixed value.
> This solution will also prevent employees from 'trying' out the parameters
> with URL Access.
> Jan Pieter Posthuma
> "David Siebert" wrote:
> > We have a number of reports which are used by both employees and
> > administrators with multiple parameters. In many of these reports we have
> > some parameters unique to the employees which we would like to automatically
> > set through URL access for our employees and either hide or set them as
> > read-only so an employee cannot view someone else's data. However, we want
> > to allow the administrators to change these values so they can view data from
> > any employee.
> >
> > So, is there any way to dynamically hide a single parameter while still
> > showing the remaining ones, or to dynamically make a single parameter
> > read-only without creating a custom front end? I don't need to know how to
> > pass default values, just how to programmatically change what parameters are
> > hidden / read-only.
> >
> > Thanks in advance.
> >
> > David

Monday, March 26, 2012

Hidding column in query

Here is my code.

SELECT [Owner].[First Name], [Owner].[Last Name], [Condo].[Unit Number],
[Condo].[Weekly Rate], [Condo].[Linens]

FROM [Owner], [Condo]

WHERE [Condo].[Linens]=True

AND [Owner].[Owner ID]=[Condo].[Owner ID]

ORDER BY [Condo].[Unit Number];

I am trying to not display "Linens" column in my query result.Any idea how
can i achive that. Thanks in advanceW. Adam (wogla@.sbcglobal.net) writes:
> Here is my code.
> SELECT [Owner].[First Name], [Owner].[Last Name], [Condo].[Unit Number],
> [Condo].[Weekly Rate], [Condo].[Linens]
> FROM [Owner], [Condo]
> WHERE [Condo].[Linens]=True
> AND [Owner].[Owner ID]=[Condo].[Owner ID]
> ORDER BY [Condo].[Unit Number];
> I am trying to not display "Linens" column in my query result.Any idea how
> can i achive that. Thanks in advance

Well, just don't display it!

Seriously, this is likely to be a GUI issue, and you should probably
ask in a forum devoted to the GUI tool you are using.

--
Erland Sommarskog, SQL Server MVP, sommar@.algonet.se

Books Online for SQL Server SP3 at
http://www.microsoft.com/sql/techin.../2000/books.asp|||"W. Adam" <wogla@.sbcglobal.net> wrote in message
news:tL5Cb.11236$aw2.5741825@.newssrv26.news.prodig y.com...
> Here is my code.
> SELECT [Owner].[First Name], [Owner].[Last Name], [Condo].[Unit Number],
> [Condo].[Weekly Rate], [Condo].[Linens]
> FROM [Owner], [Condo]
> WHERE [Condo].[Linens]=True
> AND [Owner].[Owner ID]=[Condo].[Owner ID]
> ORDER BY [Condo].[Unit Number];
>
>
> I am trying to not display "Linens" column in my query result.Any idea how
> can i achive that. Thanks in advance

There are two answers to this question. The first being, just don't select
the field

SELECT [Owner].[First Name], [Owner].[Last Name], [Condo].[Unit Number],
[Condo].[Weekly Rate]
FROM [Owner], [Condo]
WHERE [Condo].[Linens]=True
AND [Owner].[Owner ID]=[Condo].[Owner ID]
ORDER BY [Condo].[Unit Number];

- or -

If you need the linens value but don't want to display it, handle this in
business layer (class, dll, module, mts, etc.), or your presentation layer
(application, web page, etc.).

BV.
www.iheartmypond.com

Friday, March 23, 2012

Hidden parameters + automatic hiding deployment script

Hi,
I have a number of reports which hidden parameters. The problem is
that when
I change the reports, or as the number of reports grows, I'm then
having to
manually go through the report in report manager and remove the prompt
string, making sure that 'Prompt user' is checked to put the
'hidden-ness'
back.
Is there any way I could do this automatically? All the report
parameters I
wish to hide will have consistent names so it would make my life a lot
easier
if I could do this.
Can I do it through the web service - or maybe through scripting?
Any help would be greatly appreciated.
Thanks,
Phil Aldis
PS I posted this before using the MS newsgropu thing but it appears
not to have made it to google's servers so I though more people might
see this.check this script: http://blogs.msdn.com/levs/archive/2004/07/20/189178.aspx
--
This posting is provided "AS IS" with no warranties, and confers no rights.
"Phil Aldis" <philaldis@.yahoo.com> wrote in message
news:64aba0db.0409200628.95bfa1a@.posting.google.com...
> Hi,
> I have a number of reports which hidden parameters. The problem is
> that when
> I change the reports, or as the number of reports grows, I'm then
> having to
> manually go through the report in report manager and remove the prompt
> string, making sure that 'Prompt user' is checked to put the
> 'hidden-ness'
> back.
> Is there any way I could do this automatically? All the report
> parameters I
> wish to hide will have consistent names so it would make my life a lot
> easier
> if I could do this.
> Can I do it through the web service - or maybe through scripting?
> Any help would be greatly appreciated.
> Thanks,
> Phil Aldis
> PS I posted this before using the MS newsgropu thing but it appears
> not to have made it to google's servers so I though more people might
> see this.

Hidden max number of columns in Management Studio?

Hi,
The following is observed in the SQLServer 2005 Management Studio Visual
Editor:
Open table (Right Click option on a table) fails when I try it on a table
with lots of columns in it > 820 columns! Currently the table has no rows
(empty table). The same table opens fine with sql 2000 enterprise manager.
This table has been migrated/imported from sql 2000 without any errors! Other
imported tables with less number of columns can be opened in the visual
editor!
Wondering is there a hidden limit in terms of number of columns with
SQLserver 2005 Management Studio (Grid) Visual Editor?
I get SQL Executaion error
Error Source: Microsoft.VisualStudio.DataTools
Exception has been thrown by the target of an invocation
Is this a known behavior/limitation/bug? Is there a workaround?
Thanks
Kan,
See
http://www.sql-server-performance.co...ID=9016鵬
You may wish to report this as a bug at the suggested URL
http://lab.msdn.microsoft.com/produc...k/default.aspx
(also in the thread).
Steve Kass
Drew University
Kan wrote:

>Hi,
>The following is observed in the SQLServer 2005 Management Studio Visual
>Editor:
>Open table (Right Click option on a table) fails when I try it on a table
>with lots of columns in it > 820 columns! Currently the table has no rows
>(empty table). The same table opens fine with sql 2000 enterprise manager.
>This table has been migrated/imported from sql 2000 without any errors! Other
>imported tables with less number of columns can be opened in the visual
>editor!
>Wondering is there a hidden limit in terms of number of columns with
>SQLserver 2005 Management Studio (Grid) Visual Editor?
>I get SQL Executaion error
>Error Source: Microsoft.VisualStudio.DataTools
>Exception has been thrown by the target of an invocation
>Is this a known behavior/limitation/bug? Is there a workaround?
>Thanks
>
>

Friday, March 9, 2012

HelpNeed to convert number to DateTime

Hi! I'm not very technical, so please excuse me if I don't make sense...

I'm pulling Date/Time data from an Oracle database using Crystal 10, however, instead of getting a number in DateTime format, I'm getting a really long number that does not convert when using the DateTime function (I get an error stating that the year is greater than 9999.)

The number is 1123876247 (the actual date should be 8/12/2005 12:50). Sound familiar? Does anyone have any ideas on how to convert this number?

Any help is greatly appreciated!! (I'm about to pull my hair out!)How is 1123876247 related to 8/12/2005 12:50?|||1123876247 is 8/12/2005 represented in seconds since a certain date. Since my last post, I have since found that date to be 01/01/1970. So, the formula is:

DateAdd("s", (11238876247), #1970/01/01#)

This works to convert the seconds into Date/Time format.

Friday, February 24, 2012

HELP: Merge Agent failed - Error number: MSSQL_REPL-2147199402)

We have 50+ clients that use a pull merge subscription. There are 2
databases and each databases has only 1 publication. Each client has ONE
subscription to each of the 2 databases.
We had to set the retention to unlimited to avoid the following error:
The Merge Agent failed after detecting that retention-based metadata cleanup
has deleted metadata at the Publisher for changes not yet sent to the
Subscriber. You must reinitialize the subscription (without upload).
(Source: MSSQL_REPL, Error number: MSSQL_REPL-2147199402)
Get help: http://help/MSSQL_REPL-2147199402
The article http://support.microsoft.com/kb/919929/kb/919929 has a hotfix
BUT it says that it is if a Subscriber subscribes to two publications in the
same Subscriber database. This is not the case.
We had a ticket open with Miscrosoft but they were unable to find the
solution for it after 4 or 5 weeks.
The clients use their subscription databases directly and they are synced to
the server every 30 minutes.
Anybody have any idea what is causing this and how to solve this problem.
The LDF's are getting quite large and we need to find a solution soon.
Thanks in advance!
I fail to understand how the ldf's fit in here. It sounds like there are
some long running transactions which transcend the log dump boundaries. Have
you investigated what these open transactions are? Are they replication
related?
Hilary Cotter
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
"RichardD" <RichardD@.discussions.microsoft.com> wrote in message
news:B0445940-5C26-403B-8589-692458B82098@.microsoft.com...
> We have 50+ clients that use a pull merge subscription. There are 2
> databases and each databases has only 1 publication. Each client has ONE
> subscription to each of the 2 databases.
> We had to set the retention to unlimited to avoid the following error:
> The Merge Agent failed after detecting that retention-based metadata
> cleanup
> has deleted metadata at the Publisher for changes not yet sent to the
> Subscriber. You must reinitialize the subscription (without upload).
> (Source: MSSQL_REPL, Error number: MSSQL_REPL-2147199402)
> Get help: http://help/MSSQL_REPL-2147199402
> The article http://support.microsoft.com/kb/919929/kb/919929 has a hotfix
> BUT it says that it is if a Subscriber subscribes to two publications in
> the
> same Subscriber database. This is not the case.
> We had a ticket open with Miscrosoft but they were unable to find the
> solution for it after 4 or 5 weeks.
> The clients use their subscription databases directly and they are synced
> to
> the server every 30 minutes.
> Anybody have any idea what is causing this and how to solve this problem.
> The LDF's are getting quite large and we need to find a solution soon.
> Thanks in advance!
>
|||I also expect, the size of the log file has nothing to do with your
retention period.
I'm afraid I can't help on your retention period problem, but perhaps
your ldfs are growing because of a combination of the recovery model
your database is using, and your backup strategy.
Have a look at the following articles, perhaps they will help:
http://msdn2.microsoft.com/en-us/library/ms175987.aspx
http://msdn2.microsoft.com/en-us/library/ms175495.aspx
Tim Hill
On Feb 23, 6:24 pm, "Hilary Cotter" <hilary.cot...@.gmail.com> wrote:[vbcol=seagreen]
> I fail to understand how the ldf's fit in here. It sounds like there are
> some long running transactions which transcend the log dump boundaries. Have
> you investigated what these open transactions are? Are they replication
> related?
> --
> Hilary Cotter
> Looking for a SQL Server replication book?http://www.nwsu.com/0974973602.html
> Looking for a FAQ on Indexing Services/SQL FTShttp://www.indexserverfaq.com
> "RichardD" <Richa...@.discussions.microsoft.com> wrote in message
> news:B0445940-5C26-403B-8589-692458B82098@.microsoft.com...
>
>
>
>
|||You are right. I have already fixed the issue with the log files.
Regarding the error MSSQL_REPL-2147199402 we suspect that the subscribers
changed their computer date beyond 14 days (default retention) and it caused
this error.
One reason we suspect this is that out of 40+ subscribers to the one
publication, only a few had this problem and a couple of them had it happen
twice.
Does this sound like a possibility to you?
We are about to change their retention from unlimited back to 14 days. Is
there anything we should be aware of before doing this?
Thanks so much for your help.
|||Yes, we figured out the log file issue. Thank you anyway.
We are still looking for the solution for the Error number:
MSSQL_REPL-2147199402.
Any ideas?