Showing posts with label design. Show all posts
Showing posts with label design. Show all posts

Thursday, March 29, 2012

Formula problem

env: sql server 2000

objective:
add a formula for an INT column to the FORMULA field or the DEFAULT
VALUE field in DESIGN VIEW.

all of the following attempts failed
IIF (columnName = 0, "1", columnName + 1)
IIF (columnName = 0, 1, columnName + 1)
IIF (0, "1", columnName + 1)

caveat: cannot use IDENTITY
REASON: I'd like have sets of repeatable values for this row, e.g.
set a
1 -- row 1
2 -- row 2
3
4
5
set b
1 -- row 6
2
3
set c
1 -- row 9
2
3
4

Underlying rationale is to support OO design I understand probably it's
going to be huge headache for lots of people down the road but ...

TIA.NickName (dadada@.rock.com) writes:
> env: sql server 2000
> objective:
> add a formula for an INT column to the FORMULA field or the DEFAULT
> VALUE field in DESIGN VIEW.
> all of the following attempts failed
> IIF (columnName = 0, "1", columnName + 1)
> IIF (columnName = 0, 1, columnName + 1)
> IIF (0, "1", columnName + 1)

I will have to admit that I don't understand much of your post.
IIF is Access/VB, but I guess you know that.

In case not, the syntax in SQL server is

CASE WHEN columnName = 0 THEN 1 ELSE columnName + 1 END

Then again, this can be simiplied to:

columnName + 1

--
Erland Sommarskog, SQL Server MVP, esquel@.sommarskog.se

Books Online for SQL Server 2005 at
http://www.microsoft.com/technet/pr...oads/books.mspx
Books Online for SQL Server 2000 at
http://www.microsoft.com/sql/prodin...ions/books.mspx|||Oops, haven't touched db for a couple of months, now it seems that I
totally forgot everything or mix everything. Ok, joke aside, case stmt
does not seem to work, strange.|||Ahe, because of the default NULL value.

Wednesday, March 21, 2012

Formatting drill down report with varying depths of hierarchy

Good Morning, all,
I have been tasked to design reports for our budget data.
The client wants to be able to drill down through our company
hierarchy.
Some departments are five levels deep in the hierarchy, but others are
only three levels deep.
Right now a very simplified version of my dataset looks like
LEVEL0 LEVEL1 LEVEL2 LEVEL4 BUDGET
900
500000
900
600 200000
900
400 100000
900 400
250 50000
900 400
350 50000
900 400 350
612 40000
900 400 350
611 10000
So, what i want is if i drill down to 600, I shouldn't be able to
drill down any further, because there is no lower level. But if I
drill down to 400, I should be able drill down further. Right now, I
can keep drilling down two more levels below 600 until I get to the
detail level.
Can I control this with layout properties?
any ideas, suggestions, resources, war stories, or good clean jokes
would be appreciated.
KathrynFor archival purposes, I solved this by using Analysis Services to
create a cube out of my relational data. The recursive relationship
above became a dimension named Par. I created a report in Reporting
Services using the cube as a datasource. When defining the Group for
Par, you have to use two properties, UniqueName and ParentUniqueName.
These properties are created automatically when you create your MDX
query using Query Builder.. In my case, when I edited the Par Group,
I set the Group On expression to Fields!Par.UniqueName and the Parent
group to Fields!Par.ParentUniqueName. Set Visibility to Hidden and
have the Toggle Item be the textbox itself, in my case Par (which
seems recursive, but that's what you want.)
Good luck,
Kathrynsql