Problem solved?

By using a lokal sql user account on the 2000 machine it works.

I have seen referred to as "the two-hop-problem".

Can anybody explain this?

I know it works but not why...

Afterthought:

The sql server 2000 which is unreachable is on a win 2000-server.

The sql server 2000 which is reachable is on a win XP.

Can that be a clue?

/k

I have tried connection to another sql server 2000 machine.

If I have sql running under Local system or under a domain account doesnt matter,  it works on that machine.

However onto...

I am using "Be made using this security context"

And that account has adequate rights in the remote 2000 server.

/k

Thanks.

Yes, tomorrow I will stop duplicates, they were due to a front end programmer error.

The code is a simplified version from my original table, thats why it looks as it...

I finally arrived at this:

create table dbo.Numbers (

Number1 integer not null,

Number2 integer not null,

)

go

delete

from

Workaround:

DECLARE

@OrderBy varchar(33)

SET

@OrderBy = 'Number3'

SELECT

X1,

Found a workaround:

DECLARE @OrderBy varchar(33)

SET @OrderBy = 'Number3'

SELECT X1, X2 FROM

 (SELECT  N1      =  A.Number1

     , N2      =  A.Number2

  FROM  dbo.Numbers  A) X (X1,X2)

ORDER BY CASE

WHEN @OrderBy =...

Tried it on SQL2000 and also SQL2005:

--doesnt work

DECLARE

@OrderBy integer

SET

August 22, 2006 at 12:24 am