If you don't want to preserve the formatting you can save the resume and coverletter as text fields - otherwise you're better off following Remi's advice...

Here's a link to a...

The "users" are always a complaining, unhappy bunch of people at the best of times...would hate to be in your shoes after you've cuffed and gagged them...

So it's good that...

Time to whip 'em into shape then! Show them who's GOD! <;-)

Sherif - can you break up your lkup table into several ? Meaning - on the front end you have them select (eg.) continent - then display a list of...

Have to agree - there are zillions of legacy apps out there and well defined datasources are few and far between....

Alternately - you can "set dateformat":

SET DATEFORMAT ydm

GO

DECLARE @datevar datetime

SET @datevar = '2005-1-1'

SELECT @datevar

GO

Amit - good article and "nice to have" if you're stuck with maintaining databases developed by someone else.

I've had long and heated arguments with some of my colleagues on the...

While you're waiting to find the best solution, hopefully these users have only "select" permission on these tables - or better yet - a database role with specific permissions that...

How large is it ? Maybe you could load it into an array in your frontend and pass the selected value back to database for processing ?

If at all possible the datatype on that field should be changed to varchar so you don't have to rtrim each time!

You could do a differential instead of full...

Ron - I was talking specifically about David's comment on "cursors" vs. "select from every row" - not his t-sql!

Also, I've never had to personally compare performance between #table and...

erncelen - you may want to consider David's suggestion - I tried a cursor vs. a select from every row on a small table of 78 rows and even in...

This could be one way...

Create a shared drive on your remote servers - backup your .bak to this folder - map to it from your server and download the files.

An "orphan" post ????