After much testing last night - we realized that the stored procedure called by vb works correctly under SQL 2000 Service Pack 2. The customer applied SQL 2000 Service Pack 3 and now the stored procedure is broken. Any ideas what might be happening? The error is listed in the first post.