I modified the code to make sure it would work... so this is a little different than the last version. Should work with strings of any length as long as...

Sorry, but I beg to differ on your formula... How about

=Right(User!UserID,InStr(User!UserID,"\",CompareMethod.Text)-1)

I'm not sure where you got the value of 10 from... maybe the length of your servername?

As to where...

Some sample data to play with would help a LOT.

One way of doing it is this:

SELECT 100 As Amount, 'AB' AS CustomerID

UNION ALL

SELECT 200 , 'CD'

UNION ALL

SELECT 300, 'BB'

then folks...

I have a stored procedure that returns records by a patient's location in the hospital. I want to be able to return all records EXCEPT those in location = C3....

Without more details, it's hard to know what the right tool is for the job. The flexible part sounds a bit like it could be done in PowerPivot, but...

Or SSAS and Excel?

I'm sure people here can solve the problem. Like I said before, this is a classic Database 101 assignment. The point is for YOU to do it and make mistakes...

This is one of the classic schoolbook databases to learn database design. Maybe you should read one?

Sounds like you either didn't do any relational theory in class or you didn't ever read the homework assignments. This is database design 101.

What is "true" or not depends on your business rules.

The easiest way to do this is one relation at a time in your ERD. If you don't know how...

Lookups are going to bite you. Remove them all, then move to SQL Server. They don't exist in SQL Server, and didn't exist in Access for a long time. Here's...

This is a homework assignment. I know, I did it when I studied too. Do your own homework. =)

You could pivot this stuff in a Matrix in SSRS and be done already. Is that not an option? Wouldn't be if you had to output this result for...

How many possible combinations are there for "formula"? You could write a CASE statement that determined which formula to use to calculate the answer... surely must be faster than a...

Took me a minute... if you use Windowing functions (requires SQL 2012 or later), then this is easy. The PARTITION basically groups the records together... then you can use...