I'm sorry guys - I carried on looking at this and and found the issue. the issue was not with the stored procedure call but with my test data. Strangely,...

I thought I had cracked this issue but now....

and DE_Date between

'20140906' and '20140906'

This is being read as The 9th of June by SQL server.

After I looked around...

sorry my mistake - the error occurs from SQL but only when I run it through my vb.net code. Using profiler if I execute the traced procedure it works!

I took your advice:

these dates result in an error:

@dtStart='20140418',@dtEnd='20140418'

The conversion of a varchar data type to a datetime data type resulted in an out-of-range value.

Thanks

Simon

Hi,

Thank you for the replies.

I have looked at the default language for the login. This was British English, so I assume I am okay there. Interestingly if I do...

Alas that was my problem - Thank you everyone for your help.

My database compatability level was set to (80) after setting it to 100 everything worked as expected.

thanks mister.magoo.

Thanks. They are what I'm using 🙂

Well I'm please there is nothing wrong with my function\query 🙂

10.50.4000.0 2008R2 DEV

I have replicated the problem using the below table:

CREATE TABLE [dbo].[Core_Property_Details](

[CPD_UPRN_ID] [nvarchar](20) NOT NULL,

[CPD_UPRN] [nvarchar](20) NULL,

CONSTRAINT [PK_Core_Property_Details1] PRIMARY KEY CLUSTERED

(

[CPD_UPRN_ID] ASC

)WITH (PAD_INDEX = OFF, STATISTICS_NORECOMPUTE =...

Thanks for the quick response.

Unfortunately I am already running them separately.

weird.