Hi Alan,

Seem to recall checking your admin rights on which ever server you've got R6 installed onto matters.

Once you've ensured that you have full read/write & create (esp) then you'll be able to view the backup location & run a backup.

I think that's what worked for us in the past, sorry no more help,

Rob.

Once we switched to SQL2005 Express we used the command line utility to run overnight backups. We used the Windows scheduler to fire a batch file that ran the command to perform a backup. It worked very well, although it did seem to tie up the CPU at 100% usage while the backup was running. Since switching to the full SQL2005, we're now using the built-in backup tools and scheduler.

Incidentally, have you tried using the backup database function within Management Studio? If you right-click on the NBNData database, there should be a backup option in there somewhere.

Charles

Alan

That's because the SQL Server process is not running under your user account, its running under a special account that by default can only see your local disks and will have no network access. This is a security measure which prevents hackers damaging the rest of the network if they manage to run some SQL code.