Search

[finnstyle]

One of our databases was having trouble autosaving the last couple days. Then all of a sudden today it won't save at all, it says "error saving file - unable to move file(183)" and if we try deleting it, it says that someone is using the file, even though it's only open on my computer. We were able to save it in a different location, and there it saves fine, so we can continue to operate, but now we have an unusable SM file.

[David Johns]

finnstyle,

We are looking into that.  I guess it swung from one extreme to another - before the recent changes in the beta it was possible to have to read-write instances.  Now with the changes it is possible to have none!  Sorry about that.  We are working to get it just right.

Thanks for the feedback and your patience.

David

[David Johns]

finnstyle,

We have made some improvements to the save function that will probably overcome this problem.  You will be receiving notice of version 1.1.3.4 being ready to update to.  Please keep us posted as to whether this error re-occurs.

Thanks,
David