Solved. Logins, users, schema and database owners are all okay.

The issue that I'm having is that I have the original database hard coded in the stored procedures. I was fooled...

Yes, I didn't create any logins. Neither server logins nor database users. I was following the example where I restored a production database and apart from having to create a...

Yes, I ran exec sp_change_users_login 'report' with the focus on the new database. It didn't return anything.

Profiler didn't give me any new information. The SPID was correct.

Let's remove the application...

Larry, I can change the connection string to point to a restored copy of the production database and it works fine. Two things are different. This database came from a...

Perry, I ran

but it returned nothing.

George, the server logins all default to master. I did this to ensure the application didn't get steered in...

Perry, I ran this and it returned nothing. I see this is part of an...

On this server I have one instance of SQL Server running and including the new database, three databases.

When a database is restored it is owned by the user performing the restore. Since I was running SSMS as sa when I perform the restore, the new database owner...

Thanks for your reply. I'm sure the application is pointing to the new database because of the error message when I delete the user. The message tells me that the...

I'm using SQL Server 2008.

To get the script to work for decimal numbers like 35.12, I had to change

when isnumeric(ExtRef) = 1 then ExtRef

to

when isnumeric(ExtRef) = 1 then...