Simply Accounting Pro 2009 Updates

Hi Guys,

Anyone know where I can get Simply Accounting Pro 2009 Version F update? And if not can anyone tell me if a Version F data file can be converted back to Version B which is the version on the original installation disk.

Any help would be appreciated.

Thanks

Parents
  • 0

    Hi allyg,


    Simply Accounting 2009 release F update link

    http://cdn.bestsoftware.com/ftp/sa/payrollupdates/sa_2009fcpup1.exe

    Hope this helps

  • 0 in reply to Keith L

    Honestly, pay the $250 and get the latest version. You are putting your data at risk by running such an old software. If you don't need to update every year, fine, but you should be within 2 - 3 years of current software at all times.

  • 0 in reply to AmyGurl

    Sorry to jump in here and I don't mean to be argumentative, but AmyGurl, how is 2009 data at risk now more than in 2009?  Other than losing the installation programs as the OP did, I just don't see it.

    I don't dispute updating to keep up with the current rules when the rules force fundamental changes to the program, but you are talking about me updating at least 2 of my clients from SA2008 and I think probably three from SA2010 as well who have been running just fine for years.

  • 0 in reply to Richard S. Ridings

    Thank you to Keith and thank you to Richard.

    I thought AmyGurl was being a bit judgemental. I only have one client using SA2009 and it has been working perfectly up until a few days ago.

  • 0 in reply to allyg

    Being on the latest release of everything is usually nicer.

    On the other hand, upgrading to the latest release periodically can be painful -

    It's nicer to use Office 2013, than Office 2007, but now that no-one at the site is able to email anything, from any version of Sage 50, the I.T. consultant points at Sage, Sage points at Microsoft, Microsoft ignores everyone, no-one seems to be able to fix it without using FDISK...

    not so nice.  

    So if it ain't broke, don't let your consultant touch it.

  • 0 in reply to RandyW

    RandyW - so using Sage 50 2015 is seemingly incompatible with Office 2013?

    I'm using Sage 2014 version and MS Outlook 2010 currently, will be upgrading to Sage 2015 around Dec/14 and thinking about upgrading the MS Office 2013 or perhaps Office 365 (for online capability).

  • 0 in reply to RandyW

    but in my case, on the same computer

    quickbooks can email with windowsLiveMail Version 2012 (Build 16.4.3528.0331)

    but sage2014 and 2015 can't, the error "email program must be mapi-compatible and the default mapi client"

    yet, I can create an ms-access function to successfully email using WLM

    oops.. finger pointing at Sage again....

  • 0 in reply to Smith and Co

    The main point I was aiming for, was that upgrades can be painful.  If there's no immediate *need* to upgrade, why not leave well enough alone? 

    I've often enough been well ahead by building a new system, then moving the data over.  Like buying a new house instead of renovating, it's more expensive but way, way fewer surprise 'gotcha's.

    Separate from this client, where exactly one of a half dozen 'identical' Windows 8.1/64 bit workstations can email from Sage 50,

    I have Office 2013 and multiple years of Sage 50 (2007 to 2015.0) on a laptop, and on a desktop in my office.  Both are 64 bit Windows 7, both have 32 bit Office.  Both are running plain old Windows Defender.

    The 64 bit Windows 7 laptop works fine, every time, can email from all years / versions of SA.  The desktop fails instantly, every time, with an error that it can't communicate to MAPI:

    There's no error logged, nothing obvious in ProcMon.  It creates the PDF, then just... doesn't email it.  For troubleshooting, it'd be great if Sage hadn't pre dumbed-down the error message, and I could know exactly what happened.   I once saw an error message in another program "SOMETHING HAPPEN!"  which is not as eloquent, but not any less helpful.

    Probably Sage 50 is trying to send data to / through a 64 bit DLL, which can't even almost work.   And yeah... It works with QuickBooks on my system too.   And with Word, Excel, etc., etc. 

Reply
  • 0 in reply to Smith and Co

    The main point I was aiming for, was that upgrades can be painful.  If there's no immediate *need* to upgrade, why not leave well enough alone? 

    I've often enough been well ahead by building a new system, then moving the data over.  Like buying a new house instead of renovating, it's more expensive but way, way fewer surprise 'gotcha's.

    Separate from this client, where exactly one of a half dozen 'identical' Windows 8.1/64 bit workstations can email from Sage 50,

    I have Office 2013 and multiple years of Sage 50 (2007 to 2015.0) on a laptop, and on a desktop in my office.  Both are 64 bit Windows 7, both have 32 bit Office.  Both are running plain old Windows Defender.

    The 64 bit Windows 7 laptop works fine, every time, can email from all years / versions of SA.  The desktop fails instantly, every time, with an error that it can't communicate to MAPI:

    There's no error logged, nothing obvious in ProcMon.  It creates the PDF, then just... doesn't email it.  For troubleshooting, it'd be great if Sage hadn't pre dumbed-down the error message, and I could know exactly what happened.   I once saw an error message in another program "SOMETHING HAPPEN!"  which is not as eloquent, but not any less helpful.

    Probably Sage 50 is trying to send data to / through a 64 bit DLL, which can't even almost work.   And yeah... It works with QuickBooks on my system too.   And with Word, Excel, etc., etc. 

Children
No Data