Accoring to the books online, error 208 = invalid object name

Are you specifying the owner of the stored procedure when executing it?

Like

EXECUTE dbo.USP_TESTING

instead of EXECUTE USP_TESTING (looks for an object...

can you remove the @ at

cmd.Parameters.Add("@login", SqlDbType.NVarChar, 255) ...

I guess ado adds it by itself.

there is a "split" function in the scripts section that is able to split a string in seperate items

A stored procedure could

1) insert the splitted items in a temporary table

2)...

Without affecting the final result -> means the same result at the end  <> the same path used to get the same result.

inner join only red and marbles-> collect all marbles from...

till I find some reference

The reason why a restriction on the join probably performs better because it eliminates (some) rows SQL server has to retrieve / compare. This results in...

you can put the anti-open in the autoexec macro

If this one exists, it will be executed first.

Have a look at securing Access sites how about to hide the main...

In that case, contact the creator/vendor of the application and have those errors checked on severity.

Happy to help

1) Is there a firewall in between (like xp sp 2 firewall)?

2) Can you connect via ipadres\instance name?

hmm

normally a fresh install of sql server allows buildin administrators (local administrators of a pc) to login via windows authentication.

What is the estimated query plan?

Is there an index on AT1.Field2 and BT1.Field2?

Is it the only statement running on database B (since MSDE has quite some limitations)?

These would normally result in...

Is the hint really necessary?

Login failed for user SA is sql authentication.

Sure you haven't changed the password for SA?

Can you login using windows authentication?

Also have a look at the CASE statement (acts like an if).

Also consider splitting up your processing to set-based solutions.

example:

SELECT 'ABC' WHERE myfield1='A'

SELECT 'DEF' WHERE myfield2 ='B'

SELECT

   CASE myfield1='A'...

syntax 2 has more chance to perform better and it is more readable.

since you use inner joins, you could trim it to

SELECT RTrim(CONTACT.LName) + ', ' + CONTACT.FName AS 'Contact...