since [claim] is actually a varchar, you should make your comparisons the same data type:

when [claim] = 1 should be when [claim]='1'

or when it has versions appended to it:

when substring(claim,1,1)...

because of email size constraints, i would suggest having the job FTp the file to another location instead.

many email servers have a 4 meg or 10 meg limit on...

could it be something as simple as the path missing a slash?

'E:ListServer.bak' might really need to be 'E:\ListServer.bak'

oops;

missing a closing parenthesis on the line above the error line:

   SET @Pdy=(select  'pkzip -a "'+ @dbname +'-' + @DY + '.zip"' +' "' +@dbname +'-' + @DY +...

I agree; post counts show a degree of dedication towards helping people, but i've seen a lot of good helpful posts from people with just a handful of posts; some...

Remember Query analyzer is just a developer utility which can display most data.

it interprets (char10) OR char(13) as a new line;

for example:

select 'text'+ char(10) + char(13) + 'vbCrLf' + char(10)...

that is not the correct syntax; the dynamic SQL Jon posted is the correct solution.

your SQL would return 'xy' for every row in the table table_ab, where Jon's statement would...

it looks to me like you are duplicating what Visual SourceSafe does. Can you force everyone to use SourceSafe in order to manage your documents and the changes that occur to...

would something like this work for you?

Create Table Employee(

EmpNO int, 

DayOfWork datetime,  

HoursWorked int, 

[Holiday Code] varchar (30)

)

insert into Employee( EmpNO,  DayOfWork,   HoursWorked,  [Holiday Code]) VALUES(1,      '07/04/2005',  0,            'GovernmentHoilday(GH)')

insert into...

there's a bit of design issue here ;

the web page that this querystring was posted to had all those values in the Request.Querystring collection in the name-value combinations you wanted, but...

if you have access to a SQL7 instance, you can use the Import/Export wizard to move the database to the SQL7 instance, then back it up, and the backup would...

I 'm pretty sure you use the SQL Native Client provider to connect only to SQL 2005 instances., but I thought the native client had a dependancy to the .NET...

there is a script in the contributions section to check if a file exists...you could adapt it from there to call your functionality:

Perform an action when a file exisits

Script...

The database has been marked as "Suspect", not "Subject"..Suspect means SQL Server thinks it is corrupt;

i think you'll have to restore it from a backup.

I always refer to it as the "tour of the desks" when an application is installed manually, vs pushing a package out via active directory or sysinternals pstools or another...