look at the fields in the insert statement.

Then look at the values you pass into the check dup proc which is just above the insert statement.

oh it's no problem.

OK I think I found the problem.

When you create the record you INSERT @EstateCLID INTO RealEstate_ID

However when you call dbo.[CentralCheckDuplicate]

You pass in @EstateID which looks at [Realestate_id]...

how does the proc stop a dup record getting inserted?

If it's this proc? please could you supply the code:CentralCheckDuplicate

another solution

Is to put an isnull acount the field and just make the value really hight 🙂

I've heard that getdate() normally has a 3 ms difference, so if the proc ran in less than 3 ms then there is a chance the dates could be the...

Is there a trigger on the table you are inserting into ?

Also how is this sp called?

Is it not being called twice at the same time?

Please could you post the code your sp?

There you have it Lynn beat me to the code post 🙂

don't worry my toes are all good 🙂

Yeah was just thinking that creating it in a CTE no summing first then grouping the cte on the new column based on...

looks like your distinct is in the wrong place.

Try this:

select DISTINCT sum(acres), case

when curage <= 5 then 'Age 0-5'

...

could you please post the whole error message:-)

ooops well spotted Chris

Are you sure that the Db1 and DB2 are databases?

Second are you sure this is the exact code that you are running?

You shouldn't need a table to create a report.

If you open up an ADO recordset which is created from your Procedure then you don't need to know the columns at...

are we allowed to use temp tables for looping? If the loop has a purpose?