Importing from Access to MS SQL

Ok, I solved some problems than ran into new ones. How did I solve the initial problems (so future users can know an option):

The problem was: the data didn't show on my forum. When I checked the Tables directory on the database, I found out that everything was duplicated: the tblAuthor, for instance, appeared two times: one created by owner DBO and other by me.

Then I tried to import the data by doing Windows Authentication. Well, 6 tables weren't created correctly. Error message. Strange thing: the ones that WERE created through Windows Aut. (and that had DBO as owner) started to show on the forum - it worked!

Problem is: 6 important tables (including the one that cointains users and the Threads one) can't be imported through Windows Aut., only by SQL Authentication (my user ID).

So, what did I do?

From query analyzer, I tried to ran:

EXEC sp_changeobjectowner @objname='yourid.tablename', @newowner=dbo

for each of the duplicated tables. However, when I initially tried to change the ownership, it didn't let me, saying the dbo already had a file with that name. So I tried to delete the original dbo file, but the system didn't let me, saying the file had "references", or something like that. So I renamed the file and THEN changed the ownership to dbo. It worked like a charm: my users and topics showed up on the forum! But I could not delete the original dbo file, even after all that.

(Is there a problem about doing it that way? And how can I delete the original (now renamed) dbo file?)

Well, it didn't stop there. When I thought everything was fine, I tried to post messages on the forum and got the "Provider permission or locktype" thing on the post_message.asp, line 604. Damn. I searched this forum for a solution but couldn't find one. Every topic that had that question asked was ignored by other users. SO.... Is it unsolvable?

1. Run a Compact and Reapir on your Access database. (maybe not very important, but do it anyway)
   
2. delete your SQL Server database.
3. Create a new one
4. Use the Upsize wizard in Access to copy everything to the SQL Server Db. Use your SQL Server login details
5. Open mssql_server_setup.asp in a text editor and delete line 200-1693.
   
6. Run the script

I use a service that restricts dbo ownership. As a result, I had to go through the db and assign the same permissions dbo had to my mssgl Login ID for the db.

Wasn't just tables, but also included views, stored procedures, etc. Prior to doing that, I was getting messages similar to the last one you posted.