Hallo Ed,

I will go try this in the morning and give feedback. I am not worried about user impact, so I will try the SQL stop/start solution.

It is just strange that the SHRINKFILE command does not in fact empty the table but gives the error... why would the re-start of SQL (open/close of the file) result in something different?

Regards