What I ended up with (and this may not be optimal) is

USE [targetdb]

GO

/****** Object: StoredProcedure [dbo].[InsertDB] Script Date: 10/20/2009 14:11:58 ******/

SET ANSI_NULLS ON

GO

SET QUOTED_IDENTIFIER ON

GO

ALTER...

GOT IT WORKING NOW!

Ok. This compiles:

ALTER PROCEDURE [dbo].[InsertDB]

@AccessDB varchar(255)

AS

BEGIN

SET NOCOUNT ON;

DECLARE @SQL nvarchar(2000)

DECLARE @InsertID INT

Set @SQL = 'INSERT into dbo.ArchivedAccessDBs(AccessDB) SELECT...

Ok, tried this:

DECLARE @SQL nvarchar(2000)

DECLARE @InsertID int

Set @SQL = 'INSERT into dbo.ArchivedAccessDBs(AccessDB) SELECT * FROM OPENROWSET(BULK N''\\<servername>\DB\sskelton\' + @AccessDB + ''', SINGLE_BLOB) as Document SELECT @InsertID = SCOPE_IDENTITY();'

Print @SQL

EXEC...

I can understand why people might not like the idea of storing multiple column values in one encoded field, but it does occur to me that this would be a...

sorry, but I have to...

By Jack Handy:

"If you ever reach total enlightenment while drinking beer, I bet you could shoot beer out of you nose."

well apologies about the voice box thing - didn't know about that.  As for the aspberger's thing, I don't think it is indicitive of mental deficiency, and I don't think...

wow!  seems i stepped on a toe there.  by 'cheesy tech' i was thinking of the voice box for the computer -- just a silly hollywood touch.  as for the...

I definately think Sneakers is the best, if you want something that is actually true-to-life techie wise.  War Games next, but the tech is a little cheesy -- but they...