Viewing 15 posts - 1 through 15 (of 594 total)
quote:
works fine on sql2000.SENDEMAIL:
DECLARE @MailSubjectVARCHAR(1000)
SET @MailSubject = (@var1 +' '+ convert(varchar,datepart(mm,getdate())) + '/' + convert(varchar,datepart(d,getdate())) + ' ' + right(convert...
October 23, 2003 at 1:22 pm
quote:
Thanks jpipes. Did you go to MDAC 2.7 when you upgraded your environment?
On some...
October 23, 2003 at 7:02 am
quote:
Both MS03-031 security fix and KB 826161 will give you version 2000.80.811. If you need version 2000.80.778, you need call Microsoft to...
October 23, 2003 at 7:00 am
quote:
michaelr777 made very good point.I replaced SQLmap70.dll (File Version 2000.80.834.0) from another server (File Version 2000.80.760.0) in test server and it starts...
October 21, 2003 at 8:37 am
Good article, but I have only one disagreement. Instead of PRINT statements, I prefer to use RAISERROR. With RAISERROR, you can pass in variables to make the error...
October 21, 2003 at 7:37 am
Having similar error messages trying to get SQL Mail working... here's the thread:
Good luck!
October 21, 2003 at 7:14 am
quote:
I am developing on Crystal Reports, which fails to identify resultset fields when #temp tables are used in storedprocedures.
October 20, 2003 at 9:22 am
You can use xp_sendmail to alert an operator upon a step completing in the stored procedure in step 2. However, just to warn you, xp_sendmail (and SQLMail in general...
October 20, 2003 at 9:19 am
We are on the same environment. No issues whatsoever with going to MDAC 2.7.
October 20, 2003 at 9:16 am
quote:
Do you get valid results for xp_logininfo 'DDDD\blah' ?
No, I get same error message: