Are you running SQL 7.0? The REPLACE statement works for me the way you tested it originally. It seems like there was a setting to avoid *empty* strings.

As...

You might try something like this (I didn't actually run this in SQL so you might need to adjust it)

DECLARE @selSQL NVARCHAR(2000), @colList VARCHAR(1500)

SET @colList = ''

SELECT @colList = @colList...

I must be missing something. You are assigning values to @col001 and @col002, but never using them. Also - what happens if there are an odd number...

Ok - then I would probably use dynamic SQL.

DECLARE @selSQL NVARCHAR(2000), @Name1 VARCHAR(15), @Name2 VARCHAR(15)

SET @Name1 = 'Month1'

SET @selSQL = 'SELECT DISTINCT Month1/' + @Name1 + ', Month2/' + @Name1...

Could you post a little more of the surrounding code? Is this something where the table name is changing as well? Will next months query look at the...

Calvin, You might want to check why you are submitting duplicate responses. This happened in another topic as well.

Only Cheongww knows for sure, but it is my bet...

You can reference the temporary table the same as a permanent one within the procedure. Your "SELECT * FROM #CashIn" would produce a recordset. Test it by running...

ROCKO,

I don't see the use of a variable in the statement. Are you sure the error isn't somewhere else? Just for curiosity, why select top 100 percent? ...

Sounds like you are using an ADO object to open a file. Try reading the result into a DataSet object instead. If you must read using adoObject.Open, you...

Works the same as a normal table. Have you been having problems?

Guarddata-

We generally implement your first suggestion. If you have to walk the result sets and call another procedure to localize, it requires much more processing of the data. ...

Are you talking about part of the condition or one of the column names, or are you retrieving data into the column?

Please post a sample.

Guarddata-

Thanks Jay - I didn't read the second SQL in enough detail. Cheongww - I would suspect jpipes has given you the answer.

Guarddata-

It will be a little difficult since the user is "sa" 90% of the time (or the db owner if not SA) You should be able to review the...

Please take a look again at the first select statement...it references B2BError.warning but does not include the B2BError table. My guess is that this was a typo. Where...