Or restore a copy of the db from a month ago and use a third-party differencing program to compare this db with the current version and highlight schema differences.

From EM, click on Management and right click SQL Server Agent.  Select Properties - you can view and modify the info here.

Is this link relevant?  Sounds like similar problems ...

http://www.dbforums.com/showthread.php?threadid=986743&perpage=15&pagenumber=1

You've done it right.  I do this often - the backup should be fine (it's also worth zipping the backup before you send it - you'll see the file size...

Have you tried rebooting?  (The affected server, that is.)

This is a manual job I think.  Suggest you retire the Access db as soon as possible!

My colleague's insurance company increased his rate because he had had an accident in the previous year.  The fact that the accident was not his fault (another car ran into...

Ah yes, there are different types of cursors - it's looking like the default type is forward only, which means that the FIRST qualifier cannot be used.

Try this

FETCH NEXT FROM...

OK.  Try using FETCH FIRST as your initial FETCH statement - and you need the local variable there too:

FETCH FIRST FROM Localisation into @strSQL

When you use the FETCH command, you need to put the results of the FETCH into a local variable and then build your SQL string from that:

FETCH NEXT FROM Localisation...

Please post the error message.

Where in this code does @sql get set?

Or the simple version:

declare @strSQL nvarchar(4000)

DECLARE @EmpName varchar(100)

Set @EmpName = '"Frank Smith", "John Doe"'

set @strSQL = 'SELECT * FROM Employees WHERE EmpName IN (' + @EmpName + ')'

exec sp_executesql @strSQL

Note:...

Remi - is this your favourite function?  It seems to keep popping up.  Must read it one day and work out what's going on