I 2nd, 3rd and 4th the access option. It's easier to manage and sends less data on the network.

R u getting this error in a subquery/derived table or just like that?

Sql server must have access to the server where the file resides to be able to open it.

If you have an automated test system both for the app and the procs it's not too bad... otherwise you're pretty much srewed either way.

Well I had a clean Model db.

No dt procs to be seen.

I open a table with em.

Now I have dt procs in model.

They are listed as system procs.

I don't know...

That would be a first for you .

Sure start a new thread and I'll check it out.

Either is a lot of work... just creating the parsor seems more error prone to me than retesting the app. But then again that can be a $hitload of...

Oops... so where's the problem then??

Now you know I never worked with model to create server wide features for new db .

Thanx for the info about the time...

Reminds me of a story I read the other day. The guy wanted to order parts from a company. So without searching for it he just typed the...

He'd still have to parse the code which is error prone and slow.

My version doesn't touch a thing. Also I used a new table (that should actually be at least created once/server) so that I wouldn't select more data, hence sending another...

Glad I'm not the only one to think that... I was to disgusted to even correct it .

I don't really care, it's the same copy/paste .

This is all you need :

SQL and IIS on the same Box?