Libby,

In order to assist, could you clarify more specifically what the user group is seeing.  Are they not seeing the report in report manager?  If so, and the report is in...

Tracy,

I just realized you're using RS 2000 but I checked on 2005. 

I don't currently have a 2000 box to check against, but this might help:

http://weblogs.sqlteam.com/dinakar/archive/2007/03/28/60149.aspx

Scott Thornburg

Tracy, 

I'm not sure I understand what your desired output is.  Given that, let me make a best-guess and provide some suggestions: 

1)  Rather than using the NoRows property on the...

Another rewrite for SQL 2005 was done by Adam Machanic at

http://sqljunkies.com/WebLog/amachanic/archive/2006/10/19/24218.aspx

Scott Thornburg

Steve,

You're most welcome.  It's a good feeling to know that a post from almost a year ago is still useful to others. 

For the record, my understanding is that when...

Lance is correct on the cause and resolution of the error.

I would also suggest you relook at the table design.  Is there a reason you chose to split out UserLogin...

The code above is correct, except that the requirements seem to specify that should apply to table updates.  It does seem reasonable to capture the initial insert as well, which...

You can change databases dynamically within the context of an EXEC statement.  If the sql commands you wish to execute are the same for each database, this is fairly straightforward:

Megan,

If possible, could you post the code for the stored procedure?  It appears that something specific within the procedure itself is the cause of your error message.  The general approach...

I'm not sure if I understand what you're trying to accomplish.  The parent table of a trigger is explicitly identified in the trigger create statement:

CREATE TRIGGER tr_name

on MyTable

for insert, ....

Simply...

Denis,

Glad it worked.  You are correct -- there's no end to learning about SQL Server ... or life for that matter.

And I'm glad that I could contribute to a...

Denis,

I think I've gotten this error when aremote procedure has columns or functionality that can not be determined until runtime (e.g., uses temp tables or dynamic SQL).

This is a shot...

David,

SQL Server 2000 can use row-level, page-level, or table-level locks.  By default, the server determines the granularity of the locks, although you have manual control through locking hints.

And yes, nolock...

You're on the right track.  However, change your GROUP BY and ORDER BY clauses by removing the RES_NAME column.

With the inner joins, you will only get projects that have a resource assigned. ...

If you are willing to add a column to table CDX_CompanyDataXX, you can add a column that indicates the current version for each CDX_COM_Id row.  New column is bit or char(1)...