by default userid's are not case sensitive, passwords are !

Are you sure you're trying to connect to the correct server (your own SS2005Express)

If you can provide a servername, try .\SQLExpress

this is wrong, it should be twice [markr]

it should be

USE [master]

GO

--CREATE LOGIN [markr] WITH PASSWORD=N'roof1920', DEFAULT_DATABASE=[Roofing 92]

GO

USE [Roofing 92]

GO

drop user [markr]

go

CREATE USER...

Open a query window, copy/paste the script, modify it and run it.

USE [master]

GO

CREATE LOGIN [yourSQLUserId] WITH PASSWORD=N'T0pSecretP@ssword2', DEFAULT_DATABASE=[yourdatabasename]

GO

USE [yourdatabasename]

GO

CREATE USER [yourSQLUserId] FOR LOGIN [yourSQLUserId]

GO

ALTER USER [yourSQLUserId] WITH DEFAULT_SCHEMA=[dbo]

GO

EXEC sp_addrolemember N'db_datareader',...

Apparently there is no explicit SQL-userid (except for the default ones) in the db, but your application expects a userid and a password.

I would in this case create a new...

if the 'report' option did not show a result row, that would mean that all sql-userid's are mapped to the sqlserver server level. That's OK.

Maybe in the originating server, there...

I don't have SSMSexpress in use, but I think if you use the object browser, there is a security menu item, if you open that it will show you all...

just to add..

Make sure you have indexes that exactly match your FK-definition in the dependant table(s). (column order, column sorting order (asc/desc))

did someone alter the original northwind database to be readonly ?

perform on your sql2k :

alter database northwind set read_write;

Then stop the sql2000 instance or detatch northwind db, copy it to...

check out http://msdn2.microsoft.com/en-us/library/ms124425.aspx

it explains it all.

In this case datatype name is an alias data type.

apparently your application uses sql-authentication, not windows authentication.

use mamagement studio for ss2005 express to find out which user account is being used by the database.

maybe you can use these scripts to diagnose the problem :

http://www.sqlservercentral.com/scripts/Maintenance+and+Management/31867/

or even my article http://www.sqlservercentral.com/articles/Service+Broker/2897/

one of the top 3 rules for any rdbms: use the correct datatype !

If you know it concerns a date / time / datetime column, use the datetime datatype !...

Is there any reason why it shouldn't be ?

If you can connect to a source, you can (bulk) insert from it.

indeed, but that should not be a general practise

and these cases' hint accuracy should be re-evaluated often.

maybe http://www.sql-server-performance.com/da_email_functionality.asp can help out.