Too much distraction here... can't post fast enough now .

Unles you preffer doing a count(*) for each table which can be slow, I would suggest you keep using the index technic.

If you don't want have out of date info,...

Hey Steve, is it possible to have the nightmare stories back up on the site someday? I'd like to reread some of those..

I'm sure you'll have a few questions after this one... Don't be afraid to ask.

Here's how I open a record set that uses a stored proc

proc code :

CREATE PROCEDURE [dbo].[SPNDemo] @ObjectName as varchar(50), @id as int output

AS

SET NOCOUNT ON

SET @id = object_id(@ObjectName)

SELECT

...

I like using the sys* tables... they are in every database and it avoids the time loss of making/deleting the temp tables... and I figured that my exemple was clear...

Never be sorry for not knowing something... be even less sorry for finding the solution .

sql = "EXEC sp_NoOfRecords" &_

" @VTitle='" & VTitle & "'"

rs.CursorLocation=adUseClient

Set rs = Conn.Execute(sql)

How did it get fixed?

And how the hell did you do that?????????????

Can you tell us in what situation?

Nice trick... but I thaught that the RecordCount problem was due to the cursor and lock type, not the location. Do you have any readings on this.

BTW it's the...

That's true... experience does come at a cost.

I'd like to come in a interview and answer that question : How much experience do you have with Sql Server

A : (while...

Yup... wouldn't wanna be in the shoes of that guy when that happens.

rs.recordCount is the number of records produced by the query/stored proc that you supplied to the recordset.

Just run something like this in vb :

declare connection

declare recorset

open connection

MyRs.Open "Select *...

Please make sure you understand the implications of dynamic sql before going down that path.

Make sure you read this about The Curse and Blessings of Dynamic SQL

Which will...