Hold the phone.

>> is QA using OLE DB provider when connect to DB?

I don't know, somebody else can probably answer this in a second.  I do know that...

Yes, it is interesting, except that I wrote a sproc based on yours with a temp table and it did *not* crash <sigh>.

I just did it again.  Using a different...

>> is QA using OLE DB provider when connect to DB?

I don't know, somebody else can probably answer this in a second.  I do know that QA in Enterprise Mgr...

>>The most common reason I've had to do restrict the number of rows has been when doing operations against millions of records.

Here's another really common one: "paging" data for web...

Sorry, KC, I didn't mean to imply that you should leave out the condition as something that was significant to your issues.  I did it because I didn't have the...

Some additional information for you: this is really starting to bug me <g>, so I decided to try to repro your conditions.

1) Here is my sproc.  It is simpler than...

OK, look, KC, I am *far* from an expert on the subject of cursors, but there are two things I would consider here that might be different when you run...

If you're using an integer that's a DateDiff, then the VB expression I gave you should work.  No? Am I misunderstanding the question?

>L<

Yes, I totally do believe you it's the stored procedure. Sorry for getting off track with the date-conversion possibilities. 

As the last poster said, if you want somebody to figure...

Yeah, I know the suggestion in #1 will work, and #2 is basically an optimized version of #1, so it's a little more work than #1 but I would still...

>>I cannot remove the ".CommandType = adCmdCtoredProc

The reason you get the error if you remove that line is that you are not doing what I am asking you to do...

>>Lisa, is it what you want me to try? If so, it still bombed with "Operation is not alloed when the object is closed" @ the "If Not rst.BOF() Then".

No,...

Yep, there are probably 100 issues with parameter types.  That's one of the reasons why using conn.Execute rather than cmd.Execute is a good idea when you find you're having problems...

Jeff, I did read your code.  I know that you are handling the order by adding the year. I think you missed my point; you shouldn't need to compensate, because you have...

Thank you for explaining your reasoning, Jeff.  I respectfully disagree.

1. The order will almost always be determined externally to this expression anyway, since unless you can guarantee < 12 months...