The possibilities are endless. I got a laugh out of this one: http://www.google.com/codesearch?hl=en&lr=&q=idiot ------------------------------------------------------------------------ Are some "standards" just a way of saying, 'We do it that way because that's the way we've always done it.' ?

I use SQL Prompt at work in SQL Server 2000 Query Analyzer. It's ok. The intellisense does work, but not 100%. With the cryptic names our genius DBA's gave the table and column names (we just CAN'T teach those old dogs new tricks), it does help a lot. But when it doesn't work, like if I type too fast, it can't keep up, and just gets annoying. The intellisense in Sub-selects also get confused between table and column names. But, the company bought it, so I'll use it. But I would spend my own money on it. I'm very selective about the reality I choose to accept.

If you're using a trusted connection, then make sure you log into the machine where you are running the app with an account that is also an account on the SQL Server database. (By your error message, it looks like you may have logged in as 'Guest.') To check this, on the SQL Server instance, check in the Security folder, and add your account to the list, and in the Database Access tab, check the database that this account needs to access. If you don't have rights to add a user to the server, then you will need to ask your DBA to do it for you.

Hi Maro, I came across an article today that might help you get started. http://www.sqlteam.com/item.asp?ItemID=6881 The article was actually about trapping errors, but there are a couple of lines that may point you in the right direction: Basically, try this: declare @RC int set @rc = 0 select Column1 from Table1 select @RC = @@ROWCOUNT if @RC > 0 begin {do the second job} end I realize this doesn't solve your entire problem, but I hope it at least points you in the right direction. -DPR