goto the folder where the file exists

right click on the file, select properties

there's a couple of attribute checkboxes, one is readyonly - make sure its unchecked

Thank you for your response. I have done what you suggest, there was no change error still exists

I see you are backing up to an external drive.

Just some suggestions.

Try saving to your desktop to see if that works.

If so then try creating a new folder in the external drive and backup to the new folder to see if that works.

If the external drive is a USB flash drive then try a new flash drive.

Thank you CR bookkeeping,

Actually NO it is not an external drive, I have three drives on my system C\, D\ and G\ C\ is where all my programs are kept and G\ is where all my business stuff is kept.

I will try your suggestion and try saving to my desk top.

Try turning off the Compact Data checkbox to see if that helps.  No guarantee but it's worth the try.

Also, as a matter of procedure, I never overwrite my last backup.  If I overwrite a backup from the last time I did bookkeeping and find I have a problem, then I only have the last backup to go back to.  If that file has the same problem, I no longer have a good set of books to restore.  So I always put the date in the filename, which creates a new file all the time.  You should also get your backup off your computer in case your computer hard drives crash.

Hi maisin,

Can I assume the last suggestion by Posted by Richard S. Ridings  

on  Sun, Jan 12 2014 11:16 AM helped you restore?

For the benefit of members could you please confirm.

Thanks,

Akhtar

Tried turning off Compact Data...but no change.

No the problem still exists.

I did back up and save to my desktop and then moved the file to my regular folder. my bookkeeper is currently working on my last quarter 2013 gst/pst returns and bringing 2013 to a close ready to switch to 2014 she has the same Sage/SA as I do and we transfer the files virtually via Cross loop.

I am currently entering new sales into my system and printing temporary 2014 invoices which I will have to re-enter once the system is switched over to 2014. At the point my bookkeeper is finished on her side I was thinking I may uninstall Simply Accounting and then reinstall before she sends me the completed and up to date file from her system which I then have to "restore" onto my SA program.

Anyone know of any downsides to this action (uninstall then reinstall?) or things I should be aware of?

So you are able to backup now? Have you tried restoring that same file you moved to your regular folder to see if it will restore just to verify the restore will work? You can use a dummy data file name to restore to.

Also if you have not installed any patches since the initial upgrade to 2011 and you have all your key codes, account number etc then you should be fine with uninstalling and reinstalling.

Go into Help then About Simply Accounting and mark down the version and release nbr,  then select 'Support Info' at bottom right corner - which will bring up a box that you  can print off with all your keycodes, payroll tax effective date, etc.

What exactly is the path to the original location?  In the image in the first post, it is very fuzzy so I can't read it well but it looks like it contains one or more $.  If that is the case, try renaming the folder to not include any special characters.

"I did back up and save to my desktop and then moved the file to my regular folder"

It it works to one location, but not to another, the problem is that there is something different between the two locations.  There's nothing broken inside the Sage 50 software, this problem is outside of Sage 50, in the rest of your computer system.

...and we transfer the files virtually via Cross loop

Any backup or synchronization software, or indexing software, or desktop search, or anti-malware or anti-virus software, can interfere with a program trying to write out a file, especially if you're writing overtop of another file, even it if isn't obviously, apparently doing anything at the time.  The .CAB file format used to be common for installation files, so a program trying to change one might ring an alarm bell in your anti-virus software.

Anyone know of any downsides to this action (uninstall then reinstall?)

I seems wholly un-necessary.

Re Richard's comment about turning off compression:

The 'Compact data before backing up to save disk space' checkbox in the Sage 50 backup doesn't do anything, and hasn't done anything since at least before the 2008 software release.  It's a leftover from the floppy diskette days  (hence the '1' at the end of the filename).  Un-checking it doesn't turn off compression, and it perhaps never did 'compress' the old FoxPro database pre-2008.  Perhaps the old backup program circa 2004 used to stream all the data to an intermediate file, and it could compress, or not compress it, before streaming the result out to your floppy diskette.

Leaving the checkbox in when the software went through a major change didn't actually cause harm, and didn't cost anything, and didn't require explanation, and didn't require changing documentation, so that was probably the end of the discussion. 

It's like the switches on the old light posts in downtown Drumheller that said 'press button to cross'.  They replaced the streetlights with a 4-way stop a decade ago, but left the buttons on the old posts.  It couldn't hurt anything to press the buttons, but it just as surely couldn't help. 

"I did back up and save to my desktop and then moved the file to my regular folder"

It it works to one location, but not to another, the problem is that there is something different between the two locations.  There's nothing broken inside the Sage 50 software, this problem is outside of Sage 50, in the rest of your computer system.

...and we transfer the files virtually via Cross loop

Any backup or synchronization software, or indexing software, or desktop search, or anti-malware or anti-virus software, can interfere with a program trying to write out a file, especially if you're writing overtop of another file, even it if isn't obviously, apparently doing anything at the time.  The .CAB file format used to be common for installation files, so a program trying to change one might ring an alarm bell in your anti-virus software.

Anyone know of any downsides to this action (uninstall then reinstall?)

I seems wholly un-necessary.

Re Richard's comment about turning off compression:

The 'Compact data before backing up to save disk space' checkbox in the Sage 50 backup doesn't do anything, and hasn't done anything since at least before the 2008 software release.  It's a leftover from the floppy diskette days  (hence the '1' at the end of the filename).  Un-checking it doesn't turn off compression, and it perhaps never did 'compress' the old FoxPro database pre-2008.  Perhaps the old backup program circa 2004 used to stream all the data to an intermediate file, and it could compress, or not compress it, before streaming the result out to your floppy diskette.

Leaving the checkbox in when the software went through a major change didn't actually cause harm, and didn't cost anything, and didn't require explanation, and didn't require changing documentation, so that was probably the end of the discussion. 

It's like the switches on the old light posts in downtown Drumheller that said 'press button to cross'.  They replaced the streetlights with a 4-way stop a decade ago, but left the buttons on the old posts.  It couldn't hurt anything to press the buttons, but it just as surely couldn't help. 

Randy,

Where did FoxPro come from? :)  It was an MS Access database from version 8 to 2007. The Compact command is not the same as compression. It was the same command from in Access database utilities to compact eg. reindex, remove fluff, etc. which did usually reduce the amount of hard drive space used.  I do not believe there is an equivalent command in MySQL.

Sage won't tell me what it does anymore but I have been told it can cause some problems by someone outside Sage, so I don't recommend using it.

I stand corrected!

My reference to FoxPro came from something I had been told, and that may not have been true, about Microsoft's database engine.  The current Microsoft Access database engine first appeared at about the same time (1992-1993) that Microsoft bought FoxPro, but the timing of the releases, and the similarity in form and function doesn't mean Access runs on the same code that Microsoft once paid $173 million for.

I should have referred to it as the Microsoft JET database engine.

I think the reason that Sage won't tell you what that check box does, is that it doesn't do very much.   The code to span media probably still works (I've never had a backup that filled an entire memory stick and asked for a second one, and I haven't tried backing up to 3.5" floppies in a very long time).  

MySQL does have utilities that provide similar functions, but it seldom needs them.   I don't think there wouldn't be much use in running them, and that checkbox probably doesn't make them run.