I'm not sure I follow.

Pay_Type_ID is a two letter code; PR_Status is a one letter code. I can change PR_Status from nchar(1) to nvarchar(1) and oddly enough it executes.

I wonder why it works when I change the nchar(1) to nvarchar(1)

I'll pass that along,

Also something I noticed. Looking at the Where the second on 'PR_STATUS' is a data type "nchar(1)".

All of the 'Pay_Type_ID's are nvarchar(2). When I deleted...

I didn't do the upgrade... But I'm guessing no.

Will that impact the Where will doing a comparison?

How do you do an update to statistics so I can direct him in...

Wow, what a great idea!

I never actually thought of that; I could down load a data set limited to what I need and it would speed things up.

Thank you,

I'm updating the local table.

My first thought was replacing the view with an OpenQuery within the SP. Narrowed down the amount of data but didn't solve the problem.

I did...

thank you for your help everyone,

I appreciate it.

Not, we should be good there.

I'll test the ADO connections but so far it looks fine.

Code issues is one of my main concerns. But we've tested most stored procedures against out test environment.

Can you give me a common example of a OLDB issue or problem?

Yes we know and it has come up in discussion; the good news is that it's not my decision.

Thank you,

That worked great. We haven't upgraded yet but are close. I'm I'll make comments in my sp, Thank you again.

Sucess!!!!

Thank you,

Now I have to work out the particulars, i.e. the actual parameters to pass.

Thank you again.

I got a slimmed down version to work using EXECUTE sp_executesql.

However, I have more that 4,000 characters in the Select and...

This version of SQL Server has a 4,000 character max...

Yep, DTC is running.

If

A) Select From OpenQuery

And

B) Execute ('string') with string = 'Select From OpenQuery'

And

C) Insert Select From OpenQuery

All work

Then why doesn't

D) Insert Execute ('string')

Or Even

E) Insert Execute Stored Procedure

Work?