Hello,
A couple of times recently, we have been able to accidentally open a file that someone else has open and *not* get the usual warning that they have the file open. In the first couple of occasions, we got an error message when trying to save the file, and were asked where to save it locally. On the more recent occasion, the second person to close the file caused the loss of a day (or two) of work by the other person to get lost. Luckily, we renamed a DBK file and recovered the work.
On one of the computers, Sessions was not enabled (they are now!) and for some reason, the most recent Session file was from back in May!? This is rather odd as well, since the machine where the 2 days of work was done did have Sessions enabled to 4.
Sorry if this is confusing, but has anybody had the problem of not being warned when someone else has a file open? Most of the time, this has worked correctly, but not every time...
A couple of times recently, we have been able to accidentally open a file that someone else has open and *not* get the usual warning that they have the file open. In the first couple of occasions, we got an error message when trying to save the file, and were asked where to save it locally. On the more recent occasion, the second person to close the file caused the loss of a day (or two) of work by the other person to get lost. Luckily, we renamed a DBK file and recovered the work.
On one of the computers, Sessions was not enabled (they are now!) and for some reason, the most recent Session file was from back in May!? This is rather odd as well, since the machine where the 2 days of work was done did have Sessions enabled to 4.
Sorry if this is confusing, but has anybody had the problem of not being warned when someone else has a file open? Most of the time, this has worked correctly, but not every time...