Viewing 15 posts - 14,521 through 14,535 (of 18,923 total)
I 2nd, 3rd and 4th the access option. It's easier to manage and sends less data on the network.
August 11, 2005 at 10:18 am
R u getting this error in a subquery/derived table or just like that?
August 11, 2005 at 9:36 am
Sql server must have access to the server where the file resides to be able to open it.
August 11, 2005 at 8:03 am
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.
August 11, 2005 at 7:36 am
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...
August 11, 2005 at 7:31 am
That would be a first for you
.
Sure start a new thread and I'll check it out.
August 11, 2005 at 7:27 am
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...
August 11, 2005 at 7:24 am
Oops... so where's the problem then??
August 11, 2005 at 6:48 am
Now you know I never worked with model to create server wide features for new db
.
Thanx for the info about the time...
August 11, 2005 at 6:33 am
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...
August 11, 2005 at 6:28 am
He'd still have to parse the code which is error prone and slow.
August 11, 2005 at 6:24 am
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...
August 11, 2005 at 6:23 am
Glad I'm not the only one to think that... I was to disgusted to even correct it
.
August 10, 2005 at 10:28 pm
This is all you need :
August 10, 2005 at 8:52 pm
Viewing 15 posts - 14,521 through 14,535 (of 18,923 total)