I wish I knew...

remove , DateCol and ,@DateCol

You know how to do an insert statement right??

hmm not exactly,

(assuming you're gonna create a stored proc to do the insert) :

Insert into dbo.YourTable (Col1, Col2, DateCol, DateBefore, DateAfter) values (@Col1, @Col2, DateCol, dateadd(m, -6, Datefield), dateadd(m,...

See my other answer in the other thread.

I've given you what I found... But I don't see how this can be done in vba. I suspect it can be...

Yup, there it is :

DECLARE @Temp TABLE

(RowId int NOT NULL IDENTITY(1, 1),

Col1 varchar(20) NULL,

PRIMARY KEY...

yes :

StmtText ...

earlier : dateadd(m, -6, DateField)

later : dateadd(m, 6, DateField)

I'd just copy the statement, or make it into a view and use it in both sps.... there's just no need for a temp table in this case, the statement...

the where seems to force and index seek (removing a scan.. which is probabely the longest operation of the query).

However I can't really be sure without the relative cost to...

Just don't start another one .

Why can't you use a select to do this already?

It doesn't guarantee that you will catch all the databases in use.

That doesn't work very well.

I can't find a way to capture the err message..

Maybe this will get you started (you'll need to translate to vba) :

Sub test()

On Error GoTo...

it would surely help if I gave you this :

CREATE PROCEDURE [dbo].[SPNTest]

AS

SET NOCOUNT ON

Select Id, Name from dbo.SysObjects order by Name

Print 'Hello World'

RAISERROR (1, 0, 0)

SET NOCOUNT OFF

GO

where's the second plan?