This works for me.

Declare @Names as varchar(8000)

set @Names = 'SysObjects, SysIndexes'

--this is in your stored proc :

set @Names = ',' + Replace(@Names, ' ', '') + ','

Select Id, Name,...

What's the matter Frank... you seem a little bummed out???

Are the lines added at the top or the bottom of the code??

Also one thing to might solve the problem is to use GO and the beginning and the end...

I have no other idea taht can help you. Maybe some of the gurus can find an answer to your problem.

RPC means remote procedure call. I don't know if it has anything to do with the RPC event in the profiler that is raised when you call a stored...

have you tried?

SET @strSQL = @strSQL + ' WHERE im_id LIKE ''%'+@inputSearchText+'%''

im_name LIKE ''%'+@inputSearchText+'%''

OR im_desc LIKE ''%'+@inputSearchText+'%'''

Hmmm I tried his code and it works for me... can't see the problem from here. The only thing I can think of is that you may have 2...

A similar suggestion had already come up but the prospect of a custom error message was appreciated. But your point still stands that updates are not denied with this...

You're trigger would look something like this if you do my final idea

CREATE TRIGGER [trTest_IO_Insert] ON [dbo].[Test]

INSTEAD OF INSERT

AS

SET NOCOUNT ON

--makes sure that the table is empty and that...

This could become an automated task... but the best option is to find out why you're stuck at 30 mb... I can't help you on that matter since I never...

I have never used a splitting software for automation tasks but I'm pretty sure winrar could do it. Here's a search from download.com that could get you started on...

I haven't read the whole thread but I'm just pitching in with my first idea. Since it seems that you can send up to 30 mbs, couldn't make small...

I guess it all depends on the documentation system in place... but a well placed "this table can only have 1 row at the time for x reason" can...

No just for any developper that tries to insert in that table... The end user doesn't need to hear about this.

Thanx Jeff for the input. It shows that there's always many different ways to achieve the same result with SQL server. But even with this new solution I'd...