where's your multi-valued parameter defined? In the stored procedure or in the report? I would try using IN() with the report multi-valued parameter and see if that fixes it.

Did you see this?

Using Recursion and Date Tables to Simplify Date Logic

then you'd just filter it down (inside the CTE) so that it only returns Mondays.

Are your results already in a table?

Sounds like these are all separate questions... Could you post a script that creates and populates a table with your sample data?

If you have a Calendar table (or a table valued function to return all the dates between the start date and end date), then you can outer join your data...

Not much to go on here.  Are the databases radically different (no similar tables)? Or do they have lots of similar / same tables?

one way of doing this is to...

if a customer dont have any orders for continous 100 day period then the account consider as inactive (for the month of 100day addition to latest CustOrderDay). if no order...

Then create the queries you need in your SQL database, and then use SSIS to run the queries and output the data to whatever format and location you want. then...

you could let a user connect to SQL Server from Access and import a bunch of data from stored procedures, views, or tables (or or or), or let someone with...

SELECT  ListValue,...

FROM <table>

WHERE ListNumber = @ListNumber ;

So the table would be something like

CREATE TABLE ListValue (ListNumber INT, ListValue VARCHAR(10));

GO

INSERT INTO ListValue VALUES(1, 'A'),(1,'B'), (2,'C'),(2,'D');

Didn't Steve answer your question? Seemed pretty clear to me. you just overwrite the ID = 1234 with another value.

insert into Student (studentid,

StudentName,

StudentKey,

StudentAccKey,

StartDate,

EndDate)

SELECT 9786,

StudentName,

StudentKey,

StudentAccKey,

StartDate,

EndDate

FROM Student std

join casetype...

Sounds like a job for EXISTS (SELECT 1 FROM...) AND NOT EXISTS (...)

Then you could do something like create a stored procedure to get the data you want, then use SSIS to export it to an excel file, then schedule it to...

One way to do it is to create a stored procedure that returns just the rows and columns you want, and then call that from Excel.

you just specify the source...

Something like this? (Well, it's a starting point!)

Oh right... nearly forgot MATCHED is a T-SQL keyword, and so is USER_ID

use tempdb;
go

create table matched
(match_id int identity not null...

You're joking, right? This is database 101 stuff.

* How many days of data do we have ?  DISTINCTCOUNT(date) from your data table?

* Counts of rows by each day

SELECT c.date, COUNT(*)...