sounds like a WiseOwl tutorial... they're all on YouTube

I know this is closed, but it's better to pass the parameter to the stored procedure and filter there. Otherwise, you can send a lot of data to the...

Woudn't you specify that in your sort list?

Sort by:

column1

column2

SortParameter1

etc?

Then SortParameter1 could be a value list of the remaining column names. (Just build a function to determine the sort order...

You filter the second (cascaded) parameter based on the first parameter.

Given @param1 and @param2, the value list for @param2 is usually

SELECT somecolumn

FROM someTable

WHERE someField = @param1;

Are you trying to point at something with an arrow or underline something? Underlining is easy, but drawing arrows on something that will change shape might be tricky.

Nothing doing:

-- set up table

use tempdb;

GO

CREATE TABLE t1 (

PO_Num INT PRIMARY KEY,

DaysToTravel INT,

DaysInWhse INT);

GO

-- add some sample data for folks to play with

INSERT INTO t1(PO_Num, DaysToTravel, DaysInWhse) VALUES

(1,10,20),

(2,5,30),

(3,7,40);

-- now...

Then this should probably do it:

http://autofeupdater.com/

non-deterministic - "A property of a computation which may have more than one result."

So functions like NEWID() and GETDATE() are non-deterministic because they do not return the same result every...

What was it? (Sorry, that's just how I learn!)

SSRS will use the same sort order as the query/stored procedure you base the report on, so if you have the data sorted in your stored procedure, you're all set.

If...

COALESCE maybe? You might need to use a windowing function to get the previous row (LAG?) Something like

COALESCE(MyColumn, LAG(...))

Even if they do, so what? Just push a new front end out. Or is each user modifying his own front end? In that case, you might...

Maybe I'm missing something, because my results are different from yours... here's my SQL and results:

insert into Readings(MeterID, ReadingDate, Reading)

SELECT 4 ,'10/17/2013 12:00',5.1709 UNION ALL

SELECT 4,'10/17/2013 12:15',5.5319 UNION ALL

SELECT 4,'11/17/2013...

One thing I would do when loading the data is to timestamp the new records when inserting them.

DECLARE @TimeNow DATE = GETDATE(); -- sets the value of the variable to...

Why do you need to do that? Why not just index the ClientName/ID in the table, and then use a stored procedure to filter the data?

For example:

CREATE PROC usp_CompanyRecords

...