I totally agree with that. I'd buy a copy for sure.

Do you still have the link?

No but I would like to know which thread?

I guess you've already thaught of that but just in case :

Since you seem to need to have the server run 24/7. Can't you just recreate the sp...

As PW was stating (for extended properties) :

SELECT *

FROM ::fn_listextendedproperty (NULL, 'user', 'dbo', 'table', '', 'column', default)

.

Otherwise I would suggest you check out the INFORMATION_SCHEMA...

Just to complete PW's post, you could also look up the table SysProperties since you seem to like to do your own queries.

Have you tried killing this spid, maybe that's why you can't do anything with the proc?

KILL 55

1 - If this is a known bug then there must nbe a known cure.

2 - Access was designed to work with SQL server (among other things). Aside from...

How many logs do you have to keep in there? Unless you have a few gigs of data I don't see the point of building a new table every...

Declare @MyParam as int

set @MyParam = 6

EXEC dbo.MySP1 @MyParam output

--let's say that MySP1 set the param to 8

EXEC dbo.MySP2 @MyParam

Here's one of the best link that discuss it and why not to use it :

http://www.sommarskog.se/dynamic_sql.html

Ok now that we've helped you can you tell us why you needed to do that?

To rename the table :

exec sp_rename 'CurrentName', 'NewName', 'OBJECT'

No I missed that one Jeff. Thanx for the correction.

Hmm this can be a problem

.ActiveConnection = strDBConnectionString

You could try setting ActiveConnection to an adodb.connection object and close that object before accessing the params to see if it works.

As for...