Congrats on the big K Sushila.

Insert into....

err check goes here

--that gives you the id of the last insert in the proc, then you can use that variable in another insert.

SET @IdVar = Scope_Identity()

Well duh!!!

I bet more ram, faster drives and faster/more cpus could help too .

NP.

Sushila I'm not sure you can comprehend that number. It's almost impossible to measure.

You know how to make an insert??

It takes one insert per table you want to insert data to.

Then after each insert make sure there was no error (search for err...

Longer than you I guess .

I place my bet to 30 minutes min.

You can create a macro that will call that function and call it cleaning for dufus .

have you tried to rebuild the query with the wizard?? maybe the delete join in access is different than the one on sql server.

This is a function... just call it on a click of a button. You might also make a listbox that loads all the table names and create the "to...

Can you run the statement while the profiler is running? I'd like to know if the error is sql or access generated.

you run the statement directly on the server?

replace dbo_ with dbo.

Delete A from dbo_tblBook_inventory A inner join dbo_tblrhd_inventory B on A.drive_num = B.drive_num where B.date_verified Is Not Null

That's all I found... I'd ask a real expert the best path to do this :

ALTER DATABASE DbName

COLLATE collation_name

SQL server is case insensitive by default... I don't know how to solve the replication isssue though.

Ya I got what you really meant 2 minutes too late .