Instead of using this:

Month(Now() -1

you could use DateAdd() and subtract a month from some date, and then return all dates between the first of the month and the last.

Something like this? (You'd have to import the report into your project. It's using a connection to my dummy database, but you'd have to change it to point...

Use DelimitedSplit8K and toss all the non-numeric data? Then multiply?

I hope he's patient... osmosis takes a LONG time.

I'm so s-m-r-t!!! Good point, Scott... DelimitedSplit8K is perfect... (How could I miss something so blindingly obvious?)

I kinda hope he has to explain his answers....

CREATE TABLE MyData (

VID INT,

PID CHAR(3),

AID INT,

AMT SMALLMONEY,

VNO INT

);

GO

INSERT INTO MyData(VID,PID,AID,AMT,VNO) VALUES

(123,'XYZ',000,100.00,2),

(123,'XYZ',000,103.00,324),

(123,'XYZ',011,102.00,324),

(123,'XYZ',012,325.00,324),

(123,'XYZ',011,416.00,324),

(123,'XYZ',013,155.00,324);

Here's the create table and insert statements... now, what is the output report supposed to look like? That part...

Grasshopper,

If you post your expected result and the create table and enough insert statements to replicate your setup, it's a lot easier to help. See Jeff Moden's article[/url] Forum...

look up windowing functions in BOL. Maybe read Itzik Ben-Gan's book on it. He has a bunch of examples, and explains how to go about doing things...

What version of SQL Server are you using? You can create a running sum using a windowing function ... something like this:

SELECT Protocol

, [Year]

, Weekno

, [Weekly Count]

, SUM([Weekly Count]) OVER...

one way is to create an SSIS package that does the import and then deletes the file once the import is complete. Then you would just schedule the package...

Yes, but I clearly don't understand it.

Basically, my understanding is that I would create a new Customer record (with a new Primary Key, but with the same Alternate Key)... it...

hard to tell from the limited description, but you may need to use an OUTER JOIN instead of an INNER in your query. INNER by definition is "lossy", so...

Yup... Looks like Gail's comment to the effect of "It takes a LONG time to learn the ins and outs of SQL Server" was right on target... <g>

Phew! Now I don't feel quite so stupid.