Does it solve the opposite end of the problem (where if you open SlickEdit with an active workspace that has a network project that is not available, it locks up?)
I'm a bit puzzled by how SE 2008 is behaving on this. If I wait long enough to dismiss the errors, I can close the workspace, and exit SE - this should save a new state without the workspace. If I restart SE, it again tries to open the workspace and fails. However, if I give it access to the network project and open SE, it comes up normally, and the workspace ISN'T open! That's odd!
I think for me, the jury is still out on SE 2008, but I have 14 more days to test, if anyone can think of other things I can try.