restore going to wrong directory

I have a situation where for a returning client when I restore from a backup I go thru the usual process of selecting what directory I want it in and the name of it.  When it gets to the end and tries to open the file I get an error saying a data file is missing.  The SAJ directory shows up but no SAI file.  After much fiddling I finally discovered the proper SAJ & SAI files were in a sub directory of the SAJ file with a name of NEW.  When I open that SAI file it is all good.  It never did this when I originally did this client's books.  He had another person doing his books (who was not a bookkeeper) and there were many other things she totally messed up in Simply so I wonder if she somehow changed a setting that affects backups and restores.   Anyone have any ideas as to why it's restoring to a sub directory and not where I specified?  I am using Simply 2012 premium release E.    I created a new test file from scratch to see if it did the same thing but that one worked fine in that it restored the backup to where I specified.

  • 0

    Simply 2012 is a retired product but the backup system should work similarly to the latest Sage 50 2015 version. When a backup file is restored, the backup file remembers the path of where the data was stored at the time the company data was backed up. However, what likely happened in the scenario you described, when a backup file is restored and you click on Browse to change the destination where to restore the company data to, the program by default names the company data files to NEW.SAI and folder to NEW.SAJ.

  • 0 in reply to JimmyL

    The problem is it used to work fine.  I click browse when the screen comes that asks where you want to create the files.  I select the directory I have always used to all my sage data bases and I even type in the name of the company that it should be called.   So why then is it still creating it in another directly with the name NEW?  Why won't it create it where I told it to and what to name it?  I have no issues with any other file other than this one.